ash720 Posted March 30, 2012 Report Share Posted March 30, 2012 Hello I had a working system a while ago, but upgraded and lost the configuration in the process. I cannot figure out what I have missed. Incoming calls are fine, internal calls are fine, outgoing calls do not work correctly - they get to a recorded message saying that number is unavailable, regardless of which number I dial. I assume this is on the local telco's network, which makes me think the sangoma card and NBE are working fine. I am assuming the problem lies somehwere in the custom headers, but cannot find a working example for the UK. There are some examples posted for US providers. Without a working example or reference it could take me a very long time to try all possible combinations. Any ideas? Thanks. Quote Link to comment Share on other sites More sharing options...
pbx support Posted March 30, 2012 Report Share Posted March 30, 2012 If you have/had the SIP INVITE to BT from the working configuration, we can use the custom headers to match the same in v4.5. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 31, 2012 Report Share Posted March 31, 2012 So are we talking about SIP problems between Sangoma NBE and snom ONE? That should be independent from BT and actually be relatively simple. Quote Link to comment Share on other sites More sharing options...
ash720 Posted October 17, 2012 Author Report Share Posted October 17, 2012 I reverted to 4.3.0.5021 and everything works fine. Tried 4.5.0.1091 and all external calls get to a recorded message saying "The number you have dialled has not been recognized, please check and dial again". I have fiddled with custom headers and tried to get logs to match pre-upgrade logs. All the changes I make to custom headers, seem to make no difference. Does the problem lie elsewhere? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 17, 2012 Report Share Posted October 17, 2012 [5] 2012/10/17 12:21:57: SIP Tx udp:127.0.0.1:5066: INVITE sip:+447887532347@127.0.0.1;user=phone SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-9bbfe49fb71d06565dae28be1769e4d0;rport From: "Ashley Kimble" <sip:+441227710274@pbx.kimble.local;user=phone>;tag=55963 To: <sip:+447887532347@pbx.kimble.local> Call-ID: f351e3a0@pbx CSeq: 6533 INVITE Max-Forwards: 70 Contact: <sip:+441227710274@127.0.0.1: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/4.5.0.1090 Epsilon Geminids P-Asserted-Identity: <sip:01227710274> Content-Type: application/sdp Content-Length: 321 v=0 o=- 51044 51044 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 19594 RTP/AVP 0 8 9 2 3 101 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtcp-xr:rcvr-rtt=all voip-metricsa=sendrecv Looks "beautiful" to me; however not being the NBE expert here, we probably need the opinion of someone who knows how the NBE packet should look like--especially the +44 international prefix (maybe it needs to be represented as 0044). Quote Link to comment Share on other sites More sharing options...
ash720 Posted October 17, 2012 Author Report Share Posted October 17, 2012 Thanks for the reply. Just tried the 00 in place of a +, still the same problem. Quote Link to comment Share on other sites More sharing options...
Vodia support Posted October 17, 2012 Report Share Posted October 17, 2012 We will need to see what Sangoma is sending out on their log file, check this article on development logging for sangoma, make sure your running 4.5.0.1090. Sagoma Logging the article you will be interested in is "Enable development mode" then post the outbound call on this thread." Quote Link to comment Share on other sites More sharing options...
ash720 Posted October 17, 2012 Author Report Share Posted October 17, 2012 Please see enclosed sangoma log. Quote Link to comment Share on other sites More sharing options...
ash720 Posted October 25, 2012 Author Report Share Posted October 25, 2012 Not sure if this was a custom headers issue in the end - after some help from Snom support, the final setting that got it all to work was "Rewrite global numbers: Check domain country code" Whereas previously it was set to "use + symbol at beginning". 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.