Vodia support

Hi, we are waiting for confirmation for our SIP trunk to be activated by Intelepeer,

Hi, Sabsd Please review the following blog https://blog.vodia.com/voipinnovation_sms rule of thumb, every extension will need thier own ANI SMS, like a cell phone subscriber to send and recieve messages.

There's a fix on the way for the LDAP, we will add this to our template, if you would like to test change the values for the fanvil-sysconf.xml and the fanvil.txt for the older device, This will be included on the .xx version. Password>{ldap-pass}</Password> <TelAttr>telephoneNumber</TelAttr> <MobileAttr>mobileTelephoneNumber</MobileAttr> NEEDS TO BE ONLY TelephoneNumber <OtherAttr></OtherAttr>. NEEDS TO BE TelephoneNumber <NameAttr>cn sn givenName</NameAttr> <SortAttr>cn</SortAttr> <Displayname>cn</Displayname> <NumberFilter>(|(telephoneNumber=%)(mobile=%))</NumberFilter> <NameFilter>(|(sn=%)(gn=%))</NameFilter> <MaxHits>50</MaxHits>

Hi, Richard We only have tenant admin permission, for users to log into thier own tenant but cannot change certians settings, of course this is in a multi-tenant env. Queues and ring groups permission already available Add pernission this can already be done with policy groups Being able to add extensions or trunks

Hi, Fanex Good working with you, as VPBX mentioned customer router could be an issue, has we checked when you make an outbound call, the PBX and the phone transaction stops when we ask for authentication. Weve added an extra SIP port and set the phone too UDP, that seem to fix the registration issue and now able to make outbound calls. We could hard code the new SIP port to the template so those grandstreams can pick up those ports. I did notice some calls do make it to the phone system, which has nothing to with us if we don't get traffic from the provider. Let's explore some more, if you have a ticket open with sky, then I would check with them to see why some inbound calls make it and some do not.

There is only 1 ticket open, for FAX. API. Not 100% if the tickets got merged somehow. In anycase could you re-open the tickets you would like get resolved answered. Orange means it's open, Green means it's closed.

If you missed the Vodia speed training you can catch it here Vodia Speed training We are talking about the ACD feature called "Numbers" For info on this feature visit our blog at https://blog.vodia.com/callcenter_called_ID Enjoy!

Hi, M we don't have a away of suppresing error codes, when sending out notifications.

https://blog.vodia.com/snom_mode

Thanks, I see now what you mean now. The buttons are still programmed to the phone which is what we want, but this seems more like a front end bug where the buttons are no loading properly. Keep you posted on the next build.

It's working here, please reset the buttons then use default mode and save, Also I would recommend to .16 once more, as the build date is diffrent. You can also copy/paset the button text here and I can use it on my machine but as you can see it's working here.

Thanks for the update, we will test it here, looks like you have a button template you built for your the extensions?

Here are some examples Here you can set a holiday range 12/24-12/31 Assumuning the system time is correct you can also do the follwoing 12/24 or list the month/day/year 12/24/2022 hope this helps.

This should be under the tenant general settings.

Hi, Syukri You have 2 sections the redirection icon show on the left hand next to the DND icon, this is a fast access to call forwading which is essential to the user. The call forwarding withing the extension setting are only a few forwarding features. try using version http://portal.vodia.com/downloads/pbx/version-68.0.16.xml there was some issue with redirection where the number was not being reflected on the user settings of the extension.

Hi, it's under settings --->General Settings Groups Verison .16

Hi, Jason In the latest version http://portal.vodia.com/downloads/pbx/version-68.0.16.xml I was able to drag and drop my calls to an extension or a park orbit, this feature has been available for sometime now. Try it on the latest version and see how it goes. Check link below for quick presenation. https://drive.google.com/file/d/1TmA6mxZGh5f0wnj6-SNk00_NzGkPRn6H/view?usp=sharing

Try adding the rules to the Regular ANI rule instead of Trunk ANI. The format I am using +prefix: ani In this case, the prefix is needed in order for this to work correctly. So if I call an 813 number Vodia will show 9785569365 same result if I dial a 978 number. Cool feature, you can add as many entries as you want as well. Hamlet Collado Hamlet Collado

If you have a deployment that needs SRTP calling, then you can follow this documentation to see how's it's done with Telnyx. https://doc.vodia.com/docs/telnyx-secure-sip-trunking

Please try the following, hope this helps. 1. Create a group 2. Group members: List everyone that will have premission to recording an IVR 3. Group Scope: Here you have to tell Vodia which group do these group members can record, in this case the Auto Attendant. 4. Group permission: Here you will have a list of perms you can assign to the group, for recording an IVR use "Record audio for groups"

Hi Alan Which version are you on? It's the Hamster..

Release note for version 68.0.12 http://portal.vodia.com/downloads/pbx/version-68.0.12.xml 68.0.12 Some improvements for Fanvil phones. The X7C did not have the right names for buttons. Introduced a Fanvil-specific button mode like with other phone manufacturers, so that the generated code can be overwritten. Reject invalid SDP. When an SDP attachment was invalid in a INVITE request, the PBX would not send the response back. This will be used for TELES SBC that send Re-INVITE with T.38 and RTP. Downloading the Google contacts did not update the internal cache. Firmware paths were missing for some Yealink models. The missed SMS emails for queues did not mention what group was missing the message. When recording a PCAP on an extension, the PCAP now also contains the SIP messages from the trunk even if that call was set up first. Ad-hoc recording from the user front end did not work properly. Added support for IXICA SMS. Added better support for ALE M7. When email was selected as monthly billing method, the tenant login would wait for a timeout. Changed the handling of star codes in dial plan to provide better control over what star codes are handled with this feature. Allow the system admin to edit a global dial plan in any domain. Fixed some problems with queue stats, e.g. missed calls, determining previous days and months, history caching. Better default for tenant MoH when MoH was created for a specific tenant. Fixes for QuestBlue JSON SMS. Automatically load audio_moh files e.g. for FAX tones. Park fix: Handle different scenarios of parking a call. E.g. some phones/versions hold call before parking it, others park the active call directly, and we also don't want a previously held call or a ringing call etc. Check permission in the user front end must include the defaults as well. More control over caller-ID update depending on User-Agent. Park orbit: Local connected leg, instead of any leg to park it No need to show media errors in alerts in the user front end, console output is enough. Fixed several glitches in the front end where data was invalid.

If you run servers on AWS you can also run the Vodia public image, currently running version 68 ( You can upgrade the system to http://portal.vodia.com/downloads/pbx/version-68.0.12.xml Release notes found here https://doc.vodia.com/v1/docs/releasenotes680 scroll to button for 68.0.12 Vodia AMI image ID: ami-0f55557ae44b31572 Once the phone system is deployed open port 80 to login into the system. As usual, you will need a license to activate the Vodia phone system. If you have any inquiries, please send your request to support@vodia.com

Here's an update if others Vodia operators are looking to limit the number of calls on the trunk, shown below.

Hi, Vodia community If you have missed out on our Vodia speed training series, you can watch the video here. Vodia talks about how an Auto Attendant works and what cool new functions are avaible, the version used for this webinar is version 68, in which will be a major release for the Vodia PBX very soon! Enjoy!!