pbx support

Unfortunately we are going to discontinue that APP. Too much dependencies. We are going to fall back to our old installer and the new web update methods going forward.

Any idea if the RTP IP/Port in SDP changes between the INVITE and after the call is answered? A SIP trace may tell us the story.

Not sure which OS you are on. But sometimes the firewalls, do not like it when the executable is changed. May be some issue with the outbound rules?

The timeout means PBX could not connect to the server on 10.2.3.4:8080. Set the log level to 8 (Web Client) and you should see bit more information that can help us see what is going on.

You can set the "Remote Party/Privacy Indication:" to "Custom Headers" and then set "P-Charging-Vector:" to "Don't use header". That should take the unwanted header out. A question before we can go ahead. What is 7188888888 - domain/trunk/extension ANI? Depending on the answer, you can look at the http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers and http://wiki.snomone.com/index.php?title=Custom_Headers_on_the_Trunk to set your trunk too.

we had introduced couple of global variables in the last version (http://wiki.snomone.com/index.php?title=Coma_Berenicids_(2011-4.5.0.1050) - 3rd bullet ) to force the PBX to write the calls and legs to the file system.

Either you have customized the dict.txt file or some web pages are saved incorrectly. So, please remove( or rename) the 'webpages' and 'html' folders. Then restart the PBX.

Here is the latest version of the http://downloads.snom.net/snomONE/mac/v4.5/pbxctrl-darwin9.0-4.5.0.1065 This version has the fix for it and there are few feature that are not 100% tested. We should be releasing the next version in a week or so when we test most of the things.

I assume, that you know we are not making any pbxnsip versions anymore. The snomONE versions can 'act' like pbxnsip versions with the right licence. If you have already sorted out the license, then we will send you a snomONE version.

Wow! that seems very strange. We haven't heard this basic issue so far. I remember there was some state update issue with the ACD calls (long time ago). But the if the call was disconnected, calls list was cleared. What is the version number? Is it possible to run the wireshark (or some packet tracing) to get a full capture and see what's happening with the SIP messages?

what is the call sequence?

May be couple of weeks. If you want have to earlier, please let me know the OS. We can spin a version for you.

PBX may be using the same port(514) for the syslog client too (may be trying to force the server to be on a different system). Not sure if that is changed recently. That could give you trouble if both client and server on the same system. Give it a shot though.

There will not be any more pbxnsip builds. That was the decision made and announced around late 2010. The pbxnsip customers still can use non-snom phones under the snomONE versions. They just have to contact sales for updating their licenses.

Interesting.. we are now going back and forth here INVITE from Sangoma to PBX [7] 2012/04/23 14:49:29: SIP Rx udp:127.0.0.1:5066: INVITE sip:6478474640@localhost:5060;transport=udp;user=phone SIP/2.0 Reply from PBX to Sangoma [7] 2012/04/23 14:49:29: SIP Tx udp:127.0.0.1:5066: SIP/2.0 180 Ringing Repeat reply from PBX to Sangoma [7] 2012/04/23 14:49:30: SIP Tr udp:127.0.0.1:5066: SIP/2.0 180 Ringing Answer reply from PBX to Sangoma [7] 2012/04/23 14:49:34: SIP Tx udp:127.0.0.1:5066: SIP/2.0 200 Ok Looking at the PBX log, Sangoma is not seeing any of the replies that PBX is sending to 127.0.0.1:5066. Now, only thing is to make sure that these packets are not being dropped by Sangoma.

There should not be any difference between the windows version and the snomONE plus version. Please make sure that you do not have any custom files under the 'html' or the 'webpages' folder (these folders are available under the PBX working directory. Generally, /usr/local/snomONE for Linux versions)

All, The snomONE virtual appliance is now available at VMware Marketplace. Please take a look at the below link for more information https://solutionexchange.vmware.com/store/products/7602

Please PM and we can send you the prompts list and more :-).

You can turn on the REGISTER logs on the PBX (Admin->Status->Logging page under v4.5 versions) and see what is being sent in the REGISTER message. Generally, we accept everything under account or username field on the trunk.

Yes, found the issue and fixed it. Will be part of the next release.

Yes, it has been fixed already. But the version is not released yet.

Yes, there is some issue in that area. We will fix it in the next release.

I assume 192.168.0.12 does not have 'localhost' as the alias. So, try adding @domain name for the calling device & called devices. Ex: 8024@192.168.0.12. Make sure that 192.168.0.12 is the domain name for 8024 & 8025.

Do you have the SIP trace from phone or the PBX?

Haven't heard this issue before. If you can reproduce it, could you send us the steps? we can try the same here and feed it to engineering. BTW, does this happen on the 4.5.0.1050 too?