Vodia support

Have you tried "remote party ID" under SIP Caller-ID Presentation in your trunk settings?

Ah, OK we look at this on Monday. Thanks

Have you tried "remote party ID" under SIP Caller-ID Presentation? When the PBX redirects the call we should advertise the from field under" remote party ID" in the invite going out to the trunk provider. assuming they support this method is another questions.

Different model show the DND status differently for example model 550 show and (X) Do not disturb and the VVX phone shows a and phone with a minus red ( -) There is no way to modified it these setting are model based.

We will test this item in our lab and see if it's reproducible.

Looks like snomONE is doing its Job, for testing purpose can you re-create the trunk and assign a different password on the freepbx. in case of typos. Also if you upgrade to version 5.2.3 you can capture a PCAP from the trunk level. http://wiki.snomone.com/index.php?title=Trunk_PCAP_Generation

Thanks for the info can you also send along the PCAP?

408 timeout mean that the registration request could not be reached in a timely manner or at least attempted to try before sending the error code. Could be a DNS issue on your server not resolving the outbound proxy correctly. Other option is to use the IPV4 of the DNS to see if the trunk registers under the outbound proxy. If you need us to test this trunk so that you can set it up correctly you can send me a PM. Thanks

We encourage users to copy the whole PBX working directory afterwards all you need to do is swap the exe and the pbxctrl.dat file. or you can just copy everything else except the pbxctrl.exe and the pbxctrl.dat since it's already present on the other machine. Note: If you're migrating one machine to another you will need to reset the license at vodia.com account portal in order to activate the license on the new machine. You will only get 1 reset though.

I don't think it's possible unless you have a billing software "Third party" where the CDR can be sent to.

Well it looks like there is user authentication issue is the password correct? perhaps you can turn Encryption to "don't use TLS " [5] 14:37:43.747 EMAI: SMTP Server returned unexpected authentication result 334" 250-X-ANONYMOUSTLS 250-AUTH NTLM LOGIN

That has been remove couple version down. You can simply add agents by adding them to "All agents for this ACD " and also to "Currently logged in agents:" it's = to Administratively log in these agents and Administratively log out these agents by adding the extension there. There was no need to add these extra settings since the functionality was always there. To log them out just remove them as usual.

What portion of the trunk is not working and could you post a SIP trace of the event?

Hi, The only way to get a complete snapshot of the call history is by using the CDR feature in the admin setting, The Vodia PBX should be able to send you an email of all the calls made on the system at midnight. http://vodia.com/documentation/cdr

You can only show 2 piece of information on the phone, Caller name and number using the display method. http://wiki.snom.com.../display_method However you can use co-line to identify the trunk by using the buttons on the phone. or use a Hunt group to define more information. For example you can define Group name--Caller information For the group name you can define the trunk name so user can see this on the phone screen

They can turn the volume up on the phone that usually works?

That's correct it's only used for outbound call. For incoming calls you can control this on the phone. You can set the setting on the phone or provisioning the setting by editing the snom xml phone template. http://wiki.snom.com/Settings/display_method

Can you re-upgrade to 5.2.3 once more there is hotfix that was release but I am not sure if it's related to this. I was able to test this here and could not reproduce it.

There isn't any reason however we can test this and see if we get the same result.

Hi, Chrome has changed the way WEBRTC is deployed on its browser with its latest update, in fact they are now following Firefoxs lead in WEBRTC development. So it's back on the drawing board. I believe the next build will have a hotfix that will temporally deal with the change but it will only be functional on Chrome.

Hi, Alexandre We will test it here. Best regards

The best solution would be to make a backup of the working directory to keep all recordings. I'll send you a PM with the plus password that will allow root access to the machine.

This has been tested on version 5.2.2, not 100% sure if it's working on version 4 however you can take a look at docs for more help. http://wiki.snomone.com/index.php?title=Click_to_Dial

Can you remove the generated folder for that extension, reset the phone to factory default and retry to provisioning the phone. There is no need to open mac based provisioning, the snom 720 already has built in certificates. You can add the PBX IP in the update URL of the phone http://192.168.x.x The other procedure would be to use the PNP lan provisioning shown here. http://vodia.com/documentation/pnp_lan_prov You can also reset the phone and register the phone manually and see if there is a different in authentication behavior. If you're WAN provisioning then maybe you can send us a PM with the credential and we can try to Prov a phone here.