pbx support

Since we are running out of characters, we now support long names. The $Character for recording is "record_location"

Can you send an email to support@pbxnsip.com? We can send you the new script to work with. You can use this script until we release it with the new version.

We will take a look at it and send you with the updated script (we may be too restrictive now :-()

There was a fix provided the newer versions (in the last 2 weeks).

Here is the Windows version http://www.pbxnsip.com/protect/pbxctrl-3.3.0.3147.exe

We have seen this behavior in couple of instances. Here, in order to avoid transcoding, PBX uses G729a on both directions (remember, the phone has advertised that it can do G729a). But the phones do not switch to the codec that is seen on the RTP. If the phone can switch after change in the RTP from G711 to G729a, we will not have this problem. I think very few phones can do that now (snom is one of them I believe). So what PBX is doing is complaint to the protocol. Unfortunately, many phones are still behind on this.

We should be able to provide one for Win32 also. Probably today.

This should work http://www.pbxnsip.com/protect/pbxctrl-rhes4-3.3.0.3147 For Cent OS, please use http://www.pbxnsip.com/protect/pbxctrl-centos5-3.3.0.3147

If this happens consistently, can we get a RTP trace?

There was a minor javascript error in that version. If you supply less than 3 characters before the '.' (dot), it throws this error. It's been fixed a while ago. If you can supply the names like roger.name@company.com, you will not have any issues. But having 2 or less characters in the name before the dot is a requirement, please send an e-mail to support@pbxnsip.com. We will send you the updated script.

That trace does not contain ACK for the 200 OK message. That's why I think that the phone did not get any message from the PBX. Since you are using snom phone here, you can look at the SIP trace and make sure that the phone is getting messages from the PBX. You can also run the pcap trace on the snom phone (debugging purposes only)

You can send the trace to support@pbxnsip.com

Based on the above log, it looks like SIP messages are not reaching the phones. I do not see an ACK from the phone for the 200 OK. Please make sure that the home router is not blocking the traffic from PBX. Generally, SIP/RTP uses UDP. So you have to make sure that port UDP 5060 is not blocked and for RTP, 49152-64512 are not blocked. Please refer Admin->settings->ports page to see these values.

If you have the DIDs, you can set those values on the extension's "Account Number(s):" field. If you want to set multiple DIDs on the same extension, you can do so by separating them with spaces.

Did you check Admin->system->PSTN gateway page?

Please verify, under Admin->Settings->Logging page, Email Section has "Use same settings for all domains:". If this is set to "Yes" then you will not see the e-mail server settings under domain level.

We are trying to reproduce it in our lab so that we can see where the problem is and fix it. So far the problem has not happened in our network. Is there anything special about the install directory/recordings directory?

It works only if the service flag is in the manual mode

Check out http://wiki.pbxnsip.com/index.php/Inbound_...s_the_extension and see that helps.

If you set the log level to 7 or above and restart the PBX, you would see whether the port 69 is being used or not. Check out the last 2 lines of the below output ***** 1] 2009/02/12 21:39:23: Starting up version 3.2.0.3144 [8] 2009/02/12 21:39:23: Found interface on 127.0.0.1 with netmask 255.0.0.0 [8] 2009/02/12 21:39:23: Found interface on 192.168.2.10 with netmask 255.255.255.0 [8] 2009/02/12 21:39:23: Found interface on fe80::f5e4:129f:3257:5b81 with netmask :: [8] 2009/02/12 21:39:23: Found interface on ::1 with netmask :: [7] 2009/02/12 21:39:24: Found time zones HST AKDT AKST PDT PST MDT MST CDT CST2 EDT EST ADT AST NDT NST BST CET GMT+2 GMT+3 CST CAT IST AUS1 AUS2 AUS3 AUS4 AUS5 AUS6 GMT [8] 2009/02/12 21:39:24: Timer frequency is 500 us [1] 2009/02/12 21:39:24: Working Directory is C:\Program Files\pbxnsip\PBX [7] 2009/02/12 21:39:24: UDP: Opening socket [7] 2009/02/12 21:39:24: UDPv6: Opening socket [5] 2009/02/12 21:39:24: Starting threads [7] 2009/02/12 21:39:24: UDP: Opening socket [7] 2009/02/12 21:39:24: UDPv6: Opening socket [7] 2009/02/12 21:39:24: UDP: Opening socket on port 5060 [7] 2009/02/12 21:39:24: UDPv6: Opening socket on port 5060 [7] 2009/02/12 21:39:24: TCP: Opening socket on port 5060 [7] 2009/02/12 21:39:24: TCPv6: Opening socket on port 5060 [7] 2009/02/12 21:39:24: TCP: Opening socket on port 5061 [7] 2009/02/12 21:39:24: TCPv6: Opening socket on port 5061 [5] 2009/02/12 21:39:24: Set processor affinity to 1 [7] 2009/02/12 21:39:24: TCP: Opening socket on port 80 [7] 2009/02/12 21:39:24: TCPv6: Opening socket on port 80 [7] 2009/02/12 21:39:24: TCP: Opening socket on port 443 [7] 2009/02/12 21:39:24: TCPv6: Opening socket on port 443 [7] 2009/02/12 21:39:24: UDP: Opening socket on port 161 [7] 2009/02/12 21:39:24: UDPv6: Opening socket on port 161 [7] 2009/02/12 21:39:24: UDP: Opening socket on port 69 [7] 2009/02/12 21:39:24: UDPv6: Opening socket on port 69 ***********

I do not think you would get any response from the TFTP. On a side note, you have to restart the PBX service if you changed the TFTP port from 69 (default) to 65.

On a single domain PBX server, you can just set the outbound proxy as the PBX server address. It should work fine. If you have multiple domains on the PBX, then you would need the domain (only if you want to register against a different domain other than the localhost)

There may be browser incompatibility with that page. It should work fine on IE. What browser are you using?

Did you try different options in "Representing the Source" section of this page? These settings are applied on the trunk settings page.

No. Seeing someone else's DND is not supported(intentional)