Jump to content

pbx support

Members
  • Posts

    2,081
  • Joined

  • Last visited

Posts posted by pbx support

  1. It should generally show the names if it wasn't updated in a really older version. If it does not show up, then navigate to 'webpages' folder and open the xml file using notepad or some other editor. You can see the file name at the (almost)end of each file. Note that this is a crude method to find the name of changed file.

  2. Well, there are not too many differences between the pbxnsip and snomONE versions, even though we had few differences at some point.

     

    One main difference that still exists is the license, i.e., 3rd party phone plug and play support is now controlled by the license key. The transfers, registration restrictions on 3rd party phones have been already lifted.

  3. Since you do not have the log from the working versions, we may have to recreate it on a older version here and verify the results.

    Since we do not have the flexor/contact pad in the lab, it is getting slower to see/test which version of PBX software made this to fail. Is this something that can be downloaded or shared for testing?

     

    This post sent to the phone I assume - 172.28.1.77:4052, file = /action_connected_url?local=45%40pbx.domain.com.au&remote=%2a6017&callid=08a9273c6eda-9rycw0bd21p6&csta=8&active_url=45%40pbx.domain.com.au&active_user=45&active_host=pbx.sgk.com.au&displocal=BC&disprem=%2a6017

    Is that right?

  4. The versions that we release to the wiki are generally production ready, i.e, ran on the internal lab & production networks and some beta customers etc. Note that this may not exercise every test case out in the real world, but covers most cases.

     

    The upgrades, to most part, are smooth. But couple of upgrades have caused some heartburn. One such case is switching from 'pbxnsip' versions to 'snomONE' versions. The other case could be the trunk upgrades that we introduced on 4.5.

  5. Joined multicast group x.x.x.x is logged at level 8 of "Log General Events". If that category is set to 8, then you should see this log message.

     

    Otherwise, you should see "Could not join multicast group x.x.x.x". This is logged at level 0. So, you should see this message in case of the failure.

     

    Obviously, 2 things you can verify -

    1. Check the SIP logs on the phone. That should show you "SUBSCRIBE" message (http://downloads.snom.net/snomONE/docs/PnP_Multicast.swf)
    2. Check the PBX SIP trace to see if the SUBSCRIBE message is in the PBX log

     

    If you don't see the 1st one, then obviously the phone is not doing the multicast PnP.

     

    If you see the 1st one but not the 2nd one, then you know there is some issue(i.e., blocking the multicast) in the network or the network interface of the PBX server.

  6. Alright, now your box is running the latest .1090 version.

     

    I see a lot of

    Could not send 9215 bytes to 10.0.0.105, error code 104

     

    We have seen this if you run IE to login to the PBX. Not an issue for the PnP though. Assign the MAC address of any snom phone on one of the extensions and reset the phone (here I assume that the phone and the PBX are on the same network).

  7. The issue was /etc/init.d/snomONE was still using link as 'snomONE-ctrl'. All we had to do is to change that to 'pbxctrl' and rename the newly downloaded file as 'pbxctrl'. This solved the problem.

    This is the recommended method because with this change the future updates can be done from the PBX web interface. This is explained here - http://wiki.snomone.com/index.php?title=Software_Update#Important_Note

×
×
  • Create New...