Jump to content
Vodia PBX forum

Vodia Telephone System

Members
  • Content Count

    177
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vodia Telephone System

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Make sure the setting allow webrtc trunk is set to true in the pbx.xml file of the pbx working directory and restart the pbx after that. It was done because of security reasons. No login calls (even if they are not allowed to call out) can be a small security risk and therefore this setting is off by default. If you need it and aware of the little security risk you can turn it on as explained above. In the pbx.xml file it should read: <allow_wrtc_trunk>true</allow_wrtc_trunk>
  2. It has already been done. We will double check as to why it didn't make it to 59.4 but the next release should have it.
  3. But the presence page takes care of that, provided we are talking about the same thing. In the new interface we are considering adding the presence into in the home page but for now you can easily go to the presence page for the blf info.
  4. You have to login as a user to get a session id before using the websocket API, which can be used to monitor calls or make and hangup calls etc. You can get the session ID during login and then use that token on every subsequent call. An example is given below: hash = MD5(password); vars = { name: "auth", value: account + " " + hash }; sessId = putRest("/rest/system/session", vars); if (sessId != "") { document.cookie = "session=" + sessId; } The account (extension@domain) and password (its MD5 hash is used) are for the user login. To login, you make a REST call to "/rest/system/session" to the PBX with the variables explained above. You will get a session ID which you can then set to a cookie as shown, for all subsequent calls. I hope that solves the problem for you. Thanks.
  5. Can you please tell us what version of the PBX are you running? Because the encryption connection is 1.0 there and we have switched to TLS 1.2. At least that will rule out anything new we have done so that the problem can be narrowed with the version number of the PBX.
  6. I didn't get which phone you are using because the templates depend highly on the phone and model. But since we support so many phones and models, I am sure wheat you want to do should be possible out of the box provided it is one of the supported phones. If it is one of the supported phones, then all you have to do is go to the extension when you will set on the phone and go to buttons for that extension and give it the above values (ideally set BLF for button types which also handles speed dial). Then you have to provision (setup) that phone from the PBX so that it gets all its settings including buttons from the PBX. There are many links on our documentation page for setting up different phones and buttons etc.: https://vodia.com/doc/index Just search for buttons and provisioning, you should see docs for the different phones. I hope that helps. Thanks.
  7. On the snom phone web interface, under the identity in use, under tab RTP, check the setting "RTP Encryption:" It should be on. If it is off, that's the problem then we have to see why it is be provisioned as off and not on. Thanks.
  8. Can you please factory reset one phone (for testing) and re-provision it. The problem is the snom phones don't overwrite provisioning settings and with the new version something needs to be updated. That can be done if the phone is in factory reset mode and then provisioned. I am assuming that will be the problem. Thanks.
  9. The top save button is for the picture saving only (next to the picture). Maybe it should say, save picture.
  10. Yes there was a problem we found. It should work in the next build of the version. Thanks.
  11. These are star codes that need to be prefixed with the speed dial extension. So for example if you need to dial *87 before an extension that you want to pick up say 40, then to achieve *8740 in order to pickup the call ringing on 40 you have to give this prefix *87 in the prefix field and the parameter will be as usual the extension, 40 in this case. Thanks.
  12. Hmmm it works fine here. Which version of the pbx? 5.5.4? Thanks.
  13. I just checked it on my snom870 and it works perfectly for me. Of course it's not 320 and the firmware version could be the problem. As from the PBX log (with logging for subsription/notify set to yes), you can check if this message is being sent or not: NOTIFY sip:40@192.168.1.171:3296;transport=tls;line=ifobeqx9 SIP/2.0 Via: SIP/2.0/TLS 192.168.1.166:5061;branch=z9hG4bK-6a25066843af9e2a126370a8afd70d66;rport From: "Jeff McCormick" <sip:40@localhost>;tag=f67ec58c2f To: <sip:40@localhost>;tag=alkg5bnl7o Call-ID: 2867ab576a95-6ycvmd3xz92d CSeq: 25739 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.1.166:5061;transport=tls> Event: as-feature-event Subscription-State: active;expires=113 Content-Type: application/x-as-feature-event+xml Content-Length: 223 <?xml version="1.0" encoding="UTF-8"?> <DoNotDisturbEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"> <device>40@localhost</device> <doNotDisturbOn>true</doNotDisturbOn> </DoNotDisturbEvent>
  14. No, that is not possible at this moment. We are considering it in a future version.
  15. The location document has been added here: https://vodia.com/doc/location
×
×
  • Create New...