Jump to content

Custom Headers for BT PSTN


Recommended Posts


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?



Link to comment
Share on other sites

  • 6 months later...

I reverted to and everything works fine. Tried 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?

Link to comment
Share on other sites


[5] 2012/10/17 12:21:57: SIP Tx udp:

INVITE sip:+447887532347@;user=phone SIP/2.0

Via: SIP/2.0/UDP;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@;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer


Accept: application/sdp

User-Agent: snomONE/ Epsilon Geminids

P-Asserted-Identity: <sip:01227710274>

Content-Type: application/sdp

Content-Length: 321



o=- 51044 51044 IN IP4


c=IN IP4

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).

Link to comment
Share on other sites

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.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...