Vodia Telephone System

Where as we haven't tested it on T48 but I think it should behave the same as T46G which we have tested and works great. Unfortunately if something is set in Yealink it won't change it with provisioning which needs a clean slate, so if these things are already set, can you please do a factory reset and provision again. Of course, I am sure you already know that you have to give the MAC address of the phone to a particular extension and open that extension for MAC based provisioning. Then restart the factory reset phone and it should provision. To double check, what went in, you can go to the "generated" folder in your working directory for that domain and extension and check the file (with the MAC of the phone) to see all the settings that were provisioned. I hope it helps solve or narrow the problem. You can send us that generated file if the problem isn't solved.

Hi, Unfortunately when you deny the mic once in chrome, you have to manually go in to turn it back on again so it will ask that question again. I know it's for security but I think they have made it very counter intuitive. Anyway, in chrome, click on the three dots for the context menu, then click settings, then go to Site settings, then click on "Camera or microphone" and turn it back on.

The problem is, it works here so I am in the dark what to look at. Could you please make a clean pcap of that single call where the wireshark is running on the PBX system and the browser call is being made from any other system with the chrome. And some explanation of which IP is what device. That could be helpful since we can't reproduce it here. By the way, have you added some client side certificate to the pbx or is it all default? It is probably default and not touched but just trying to eliminate anything that could cause it.

I am assuming, your mic, speaker and relevant volumes are all fine. Also the call is completed on the other side, that is the other side phone rings and you pick it up and the status etc. changes on the page but no audio? I am trying to find out what else could have broken down if there is not even a webrtc or even our own errors showing on the page. I am also assuming you are giving the call enough time, because with ICE and now DTLS the establishment of the call takes a while. Also please refresh the page with ctrl+F5 so that nothing cached is being used. By the way does it go to the point where the browser asks you about allowing or not allowing the mic? Because as you may already know if your deny the mic once, it has to be explicitly turned on again before it will ask you for that permission again.

That is very strange because we just tested on Chrome and Firefox with that release and works great. Actually we also tested it with android chrome on a mobile phone and also worked. Windows chrome: Version 40.0.2214.111 m Hmmmm, when you are in chrome, can you please press Ctrl+Shift+J so that the debug window appears below. Then make the call and paste any error messages here.

As far as I know, I don't think so, because we generate the files on the fly. And since it works for all kinds of SPA phones, the 301 being so close to 303 should work. Are you assigning the MAC of the phone to an extension and opening that mac for provisioning before restarting the phone? And how does the phone find the PBX, option 66 or some other way? Or are you entering the correct URL in the phone for provisioning. Just a check list in case something has been missed. Here is the relevant document, if you haven't already read it: http://vodia.com/documentation/pnp_ciscospa Also, what does the pbx log say, when set only to show provisioning logs and clear it before provisioning the phone to get a clean log of what is going on.

Well we have tested it with SPA303 and it works. We have not explicitly tested it with SPA301 but it would be strange if it doesn't work on that too.

Well it works here but we don't have the model you are talking about. Although I don't see why it would be any different. Just to confirm, the phone for example sends a request like: [8] 2014/11/25 11:06:57: HTTP: Received request for file cfg000b82612345 from 99.231.107.254 where 000b82612345 is the mac address. Of course if will be your mac address but just to confirm that it is NOT 000b826xxxxx? Also can you send me what you entered in the phone's webpage setting for provisioning, just to compare? Thanks.

By the way, you changed the mac address last 4 digits to xxxx in the logs here right? Originally it was a fully valid mac address of the phone? [8] 2014/11/25 11:06:57: HTTP: Received request for file cfg000b826xxxxx from 99.231.107.254 [7] 2014/11/25 11:06:57: HTTP: Error generating or finding grandstream-reject1, Send back 404 Not Found to 99.231.107.254 [8] 2014/11/25 11:06:57: HTTP: Received request for file cfg000b826xxxxx.xml from 99.231.107.254 [7] 2014/11/25 11:06:57: HTTP: Error finding cfg000b826xxxxx.xml, Send back 404 Not Found to 99.231.107.254

And I answered very specifically that yes it IS WebRTC but not DTLS. Even within WebRTC there are two ways, SDE and DTLS and we do SDE at this moment but not DTLS. If it's feasible we will also do DTLS but not yet. That is why only chrome will work at the moment since only chrome supports both SDE and DTLS. About hitting our talk button: If you are using your chrome browser WITHOUT any special plug in or download and it is able to talk to our server and you are able to hear and speak to someone, that means there is NO OTHER WAY but you were able to connect via WebRTC. That was just to show it is doing WebRTC and nothing else. Signalling is not covered by WebRTC though. RFC 7118 seems to cover that and it seems interesting but that is not implemented yet. I hope that was clearer.

What is the pbx version? We introduced grandstream version GXV3xxx in version 5.2.3 on wards. Also we haven't specifically tested it on GXV3275, although we did test it for several other versions like GXV3240 etc.

Yes we support WebRTC, but only the SDES connection (where the srtp key is exchanged in the sdp directly) and not yet the DTLS part of it. That's why you have to use chrome, which supports both SDES and DTLS for now and therefore works. What version of the PBX are you on? Here is something about setting it up as a trunk: http://vodia.com/documentation/trunk_wrtc You can also use the "talk" button from our website "vodia.com" to call us for a quick test using chrome browser. Thanks.

The next version should have it fixed. Thanks.

Not at this moment. Right now it is only user based for each user.

Well version 3.4 is quite old and it is not always possible to maintain all the database structure from such an old version while improving and adding things to our software. We are on version 5.2.4 now and I am sure a lot has changed since then. I am afraid the full jump cannot be made but whichever things don't work will have to be recreated as you mentioned. Also, if you go to 4.5 now, ultimately you will have to face the same kind of problem going to version 5 base. So maybe, you could just go to the latest, just a suggestion, so that you do not have to repeat this process again soon. But keep in mind version 5 would mean a new license which has to be bought, if you decide to go that route. Thanks.

You should be able to find it here: http://vodia.com/documentation/lang_installation

Are you using PBX version 5.2.4? That's where we have fixed something in this area.

There are some things to consider: First of all, what do we want to enter the CRM system when making or receiving calls and in what way? There are many different combinations and everyone would like it in their specific way. So, integration is one thing but also how do we provide the flexibility to the customers to enter whatever they want and when. For example, we have already done one way of it and if it suits someone, maybe they can use it already. However it has not been vigorously tested, nor on all versions and flavors of the CRM. If you want to test it though, all you will need is a CRM license from us on one of our latest versions, preferably 5.2.4. It is implemented as follows: You enter the CRM URL (version included) in a setting together with the username and password of the account in the CRM where the entries should be made. These settings are extension based so every person who has an account in the CRM will have his/her calls recorded in his/her account on the CRM. Now, whenever a call is made or received on that extension, the PBX will record it in the CRM under calls for that extensions account with the destination number and duration. The PBX will also link the destination number to the contact that it finds in that CRM account which matches the number. And if the contact that was already entered by the user under an account, therefore it will be linked to the account in this way. The date and time of the call is already entered by the CRM system when the entry is made. The PBX makes this entry first when a call is connected with 0 duration, so that a person could check who it is (if the contact is found), and then refreshed that same entry when the call ends, so that the duration can be entered for the call. So that's one way we have done it. Another way would be to use our CSTA browser which triggers a URL in the default browser and can be used for say a CRM entry etc. Details here: http://wiki.snomone.com/index.php?title=Csta_Browser For people who may want to integrate it in their custom way, they can use our CSTA interface to get information from the PBX and also be able to control certain aspects of it. You can find details on our CSTA interface and API here: http://wiki.snomone.com/index.php?title=CSTA_api http://wiki.snomone.com/index.php?title=CSTA_example I hope it helps.

Did you search for a contact, say the name of an extension, at least the first two letters for example. Because unfortunately yealink won't show you the list. You will have to search after pressing the first two letters or so for the name you are searching. I hope it helps.

Well for me I tested it again and it works. Exchange Address set to: https://outlook.office365.com. Maybe you should test it with the same account you gave me in the private message to see if you get the 2 test contacts I created there. Maybe it could be some contact of yours is giving problems, at least it will narrow it down. By the way since the password for that account had expired, I had to changed the last two digits from 12 to 14, in case you want to test that account first. Additionally, maybe you may have to turn off certificate verification by setting Verify server certificate: to No, only if it does not first work with this setting set to Yes. Make sure to try it with Yes first. After saving the settings, press the sync and wait a little bit. That's about all I can think of right now to test ...

It uses existing files like snom_3xx_fw.xml snom_710_phone.xml snom_710_buttons.xml Those files will take care of it. I hope it helps.

Good that it works for you now. Yes we do provision them but the problem is a lot of people didn't want to press enter after most of their 2-digit star codes like DND etc. For that, two digits after * dials it automatically. But of course it creates this problem that you faced. So we'll have to think about it a bit.

So far, we support provisioning images for color display models only. So if you have VVX400 or IP670 etc. simply drop the appropriate image in the "Drop your company logo here" box under domain->logo and save. Then provision the phone. The image will be provisioned as well for both the phones, automatically using different resolutions of the same image for the different phones. If it's a single phone, you can also of course go to the phone web interface and in many cases add a background image there. I hope it helps.

Well you can modify/customize the polycom_all.xml file in admin mode under "Templates" for all domains or in domain mode under "Customize" for that domain only. Select "Type" as Phone PnP, then select your page to modify. When you customize the file this way for your purposes, this is the file that will be used. Note: Keep in mind if you do an update of the software, it will still be these files that are used, so you may want to do it again after an update just to keep up to date. Thanks.

Give you email address, password and set the setting Exchange Address (recommended to leave blank for autodiscover): to https://outlook.office365.com and try again. Save, then Sync. Please use the PBX version 5.2.3 or 5.2.3a if possible.