Happy Posted February 20, 2012 Report Share Posted February 20, 2012 Would like to get some advice : updated latest pbxnsip to snomone beta corona 2011-4.5.0.1030, using snom green (updated) licence key. Snom 320 phones updated to latest version (8-4-35). From now on impossible to make outbound calls using the voip weepee standard nor backup trunk. Any attempt ends with 'service unavailable'. I have added a trace from the log file. Trace 1 is with co-lines, trace 2 is with co-line removed. It does not work either way. Outbound dialing using a patton gateway works like always. I hope someone can give me a clue to solve the problem. Rolling back to the latest pbxnsip version makes all problems go away. Best Regards, Marc logfile snomone 1.txt logfile snomone 2.txt Quote Link to comment Share on other sites More sharing options...
venom Posted February 20, 2012 Report Share Posted February 20, 2012 When you upgrade to the new ALPHA or BETA release you lose the SIP trunk Header defaults from the older releases. You need to go into the Remote Party/Privacy Indication setting on your SIP trunk and select use custom headers. Take a look at the post below for help. http://forum.snomone.com/index.php?/topic/5705-beta-corona-austrinids-outbound-call-problem/ Good luck. Quote Link to comment Share on other sites More sharing options...
Happy Posted February 21, 2012 Author Report Share Posted February 21, 2012 When you upgrade to the new ALPHA or BETA release you lose the SIP trunk Header defaults from the older releases. You need to go into the Remote Party/Privacy Indication setting on your SIP trunk and select use custom headers. Good luck. No luck. I have been using 'Custom Headers', have been playing with the settings, but does not solve the problem. I hope the support people of snom can shead some light : I was using 'Remote-party-id' in the setting on pbxnsip. I have attached a logfile with a call, using custom headers here. But to me changing these settings is a stab in the dark, I have a rather limited Sip knowledge. Best regards, Marc. logfile snomone 3.txt Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 22, 2012 Report Share Posted February 22, 2012 Any chance that you have a similar log (working) from v4.3 or whatever version that you were using? Quote Link to comment Share on other sites More sharing options...
Happy Posted February 22, 2012 Author Report Share Posted February 22, 2012 Any chance that you have a similar log (working) from v4.3 or whatever version that you were using? I'm not sure what you mean by 'similar'. What I did was : clear the log-file, make a call, fetch the log file and send it over. I am using Pbxnsip Version 4.3.0.5021 (Win32). I just stopped the pbx and put the snomone pbxctrl.exe file in place of the other. Quote Link to comment Share on other sites More sharing options...
Vodia support Posted February 27, 2012 Report Share Posted February 27, 2012 I'm not sure what you mean by 'similar'. What I did was : clear the log-file, make a call, fetch the log file and send it over. I am using Pbxnsip Version 4.3.0.5021 (Win32). I just stopped the pbx and put the snomone pbxctrl.exe file in place of the other. Were you able to roll back to Pbxnsip Version 4.3.0.5021 and post the sip trace of your successful call here? We can determine what needs to be configure on snomone beta corona 2011-4.5.0.1030 header page by looking at the invite to the trunk provider. Quote Link to comment Share on other sites More sharing options...
Happy Posted February 27, 2012 Author Report Share Posted February 27, 2012 Were you able to roll back to Pbxnsip Version 4.3.0.5021 and post the sip trace of your successful call here? We can determine what needs to be configure on snomone beta corona 2011-4.5.0.1030 header page by looking at the invite to the trunk provider. This is Sip-trace of a successful call to the provider using pbxnsip: [5] 2012/02/27 22:32:55: Dialplan "Algemeen Kiesplan": Match 0495123456@pbx.praktijk.be to <sip:0495123456@ssw0.brussels.weepee.org;user=phone> on trunk WeePee [5] 2012/02/27 22:33:06: INVITE Response 487 Request Terminated: Terminate 7b7c5aa6@pbx [5] 2012/02/27 22:34:56: INVITE Response 487 Request Terminated: Terminate c76e272a@pbx Detailed log-file as attachement. Best Regards, Marc logfile pbxnsip.txt Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 27, 2012 Report Share Posted February 27, 2012 Ok, With 4.3 PBX is sending [7] 2012/02/27 22:39:12: SIP Tx udp:91.208.12.130:5060: INVITE sip:0495123456@ssw0.brussels.weepee.org;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.1.15:5060;branch=z9hG4bK-60f9c4aa04ed83ce12a9e6bf7514ae34;rport From: <sip:011512345@ssw0.brussels.weepee.org;user=phone>;tag=33913 To: <sip:0495123456@ssw0.brussels.weepee.org;user=phone> Call-ID: 9287a6b9@pbx CSeq: 1938 INVITE Max-Forwards: 70 Contact: <sip:329901234567@192.168.1.15:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/4.3.0.5021 Remote-Party-ID: "Bureel" <sip:011512345@pbx.praktijk.be;user=phone>;party=calling;screen=yes Content-Type: application/sdp Content-Length: 300 With 4.5 PBX is sending INVITE sip:0495123456@ssw0.brussels.weepee.org;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.1.15:5060;branch=z9hG4bK-f5f81c59b5e4aa61699174fb18c92e2a;rport From: <sip:329901234567@ssw0.brussels.weepee.org>;tag=788 To: <sip:0495123456@ssw0.brussels.weepee.org> Call-ID: 330ff5e6@pbx CSeq: 27268 INVITE Max-Forwards: 70 Contact: <sip:329901234567@192.168.1.15:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snomONE/2011-4.5.0.1030 Beta Corona Austrinids Remote-Party-ID: "Bureel" <sip:011584006@pbx.praktijk.be;user=phone> Privacy: id P-Charging-Vector: icid-value=;icid-generated-at=192.168.1.15;orig-ioi=pbx.praktijk.be Content-Type: application/sdp Content-Length: 300 As you can see, in 4.3, both From and Remote-Party-ID have the same user name. Now, if the provider expects 011584006 in the From header, then you have to choose the same option on the "From" drop-down (i.e., if the "Remote-Party-ID" is set to "Based on the incoming call", then choose the same for the "From" header drop-down. If the provider wants the trunk domain instead of PBX domain in the From header then you can setup something like <sip:{from-ani}@{trunk-registrar};user=phone>. As I mentioned different parameter-value combinations are listed here http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers At the end of that help page, it talks about how to use the Other drop-down option. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.