Jump to content

pbx support

Members
  • Posts

    2,081
  • Joined

  • Last visited

2 Followers

Profile Information

  • Gender
    Male

Recent Profile Visitors

22,165 profile views

pbx support's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. We tested the same scenario here with the same snomONE software and with phone version 8.7.3.10 (that's what was running in the lab). Everything worked without any issues. On the IP address topic, are you referring to the "Accounts" page? Then these IP addresses are reported by the phones in the REGISTER message using "WWW-Contact" header. So please check the REGISTER messages coming from the phone to see if they are reporting the right info.
  2. Probably the DTMF is not being transmitted to the PBX with the new setup. That's why when the customer presses 1, nothing happens. Meanwhile, you can make use of the"AA->Redirect number & AA->Timeout(s)" fields to forward/redirect the call to either sales or accounting so that you do not miss any calls.
  3. http://forum.snomone.com/index.php?/topic/6359-the-mos-detailed/ was the link.
  4. Not sure if you checked the text in front of the link. It says - (will be released soon!). Probably it is not uploaded yet.
  5. Couple of things - First check if you can download the http://provisioning.snom.com/download/fw/snom760-8.7.3.10-SIP-r.bin from your phone network. On the phone, Advanced->Upgrade page, make sure that "never update.." is not set. Sometimes, a reset(instead of a reboot) of the phone would help clear everything out and thereby making this process easier.
  6. http://wiki.snomone.com/index.php?title=OEM should provide you with the instructions.
  7. We have not worked on this feature so far.
  8. You should see "Firmware for snom 720:" field in that page. The 4.5.0.1090 version comes with http://provisioning.snom.com/download/fw/snom720-8.7.2.9-SIP-r.bin. You can modify this field to point to the new 8.7.3.10 version (just copy the firmware download link here). Same goes for 760 too.
  9. It used to get redirected to www.snom.com. Looks like something has changed.
  10. In this case we/you really have to look at the RTP streams (In/Out). If the streams are different, then on some devices you will see this issue. The "Lock codec" (at the Admin->Settings->Ports page) supposed to take care of this very issue, i.e., if the phone is doing codec A and if the trunk provider is doing codec B, PBX will transcode codec B to codec A and send it to the phone.
  11. You can setup the 2 service flags (one for week days and other for Saturday and Sunday) and then use those under the "AA->Night service" section to forward the calls to respective hunt groups.
  12. If this is still an issue, can you capture a registration log between the PBX and the provider?
  13. Is the trunk registered properly? The below message is indicates that the trunk is not registered. [5] 2012/09/14 08:32:28: Registration on trunk 2 (Trunk SIP) failed. Retry in 60 seconds
  14. Ok, we will add the bulk delete option to access list too. (next version)
×
×
  • Create New...