I have a SIP Trunk with one register statement which handles 400DIDs (new installation).
On incoming calls the SIP Provider will send an INVITE to the Registered Username (which happens to be a 10 digit number), but with the actual dialed number in the TO Header. Unfortunately when the Adtran sends the call out via the PRI it is sending the Dialed Number from the INVITE instead of the TO Header. The result is a rejection from the local PBX. See below:
debug on sip trunk
18:17:34.786 SIP.STACK MSG INVITE sip:5555555555@10.5.5.5:5060;transport=UDP SIP/2.0
18:17:34.787 SIP.STACK MSG Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bK290hka10e8j11dn7k0k0.1
18:17:34.788 SIP.STACK MSG From: "Test "<sip:9541112222@as1.voip.evolveip.net;user=phone>;tag=1574552918-1430345854933-
18:17:34.788 SIP.STACK MSG To: "Customer"<sip:2222222222@voip.evolveip.net>
debug on PRI
18:17:34.837 ISDN.L2_FMT PRI 1 ==============================================
18:17:34.838 ISDN.L2_FMT PRI 1 T Sapi:00 C/R:C Tei:00 INFO Ns:94 Nr:113 P:0
18:17:34.838 ISDN.L2_FMT PRI 1 Prot:08 CRL:2 CRV:0020
18:17:34.839 ISDN.L2_FMT PRI 1 M - 05 SETUP
18:17:34.839 ISDN.L2_FMT PRI 1 IE - 04 BEARER CAPABILITY Len=3
18:17:34.839 ISDN.L2_FMT PRI 1 80 Xfer Cap.:SPEECH
18:17:34.840 ISDN.L2_FMT PRI 1 90 Xfer Rate:64k
18:17:34.840 ISDN.L2_FMT PRI 1 A2 Layer 1:G.711 U-Law
18:17:34.840 ISDN.L2_FMT PRI 1 IE - 18 CHANNEL ID Len=3
18:17:34.841 ISDN.L2_FMT PRI 1 A1 Primary Rate
18:17:34.841 ISDN.L2_FMT PRI 1 Intfc ID:IMPLICIT
18:17:34.841 ISDN.L2_FMT PRI 1 Pref/Excl:PREFERRED
18:17:34.841 ISDN.L2_FMT PRI 1 D-Chan Indicated:NO
18:17:34.842 ISDN.L2_FMT PRI 1 Chan. Sel:FOLLOWS
18:17:34.842 ISDN.L2_FMT PRI 1 83 Numb/Map:NUMBER
18:17:34.842 ISDN.L2_FMT PRI 1 8e Channel:14
18:17:34.843 ISDN.L2_FMT PRI 1 IE - 1C FACILITY Len=27
18:17:34.843 ISDN.L2_FMT PRI 1 Calling Name: Test
18:17:34.843 ISDN.L2_FMT PRI 1 IE - 6C CALLING PARTY # Len=12
18:17:34.844 ISDN.L2_FMT PRI 1 00 Numb. Type:UNKNOWN
18:17:34.844 ISDN.L2_FMT PRI 1 Numb. Plan:UNKNOWN
18:17:34.845 ISDN.L2_FMT PRI 1 80 Presentation:ALLOWED
18:17:34.845 ISDN.L2_FMT PRI 1 Screening:USER PROVIDED
18:17:34.846 ISDN.L2_FMT PRI 1 Ph.# 9541112222
18:17:34.846 ISDN.L2_FMT PRI 1 IE - 70 CALLED PARTY # Len=11
18:17:34.847 ISDN.L2_FMT PRI 1 80 Numb. Type:UNKNOWN
18:17:34.847 ISDN.L2_FMT PRI 1 Numb. Plan:UNKNOWN
18:17:34.847 ISDN.L2_FMT PRI 1 Ph.# 5555555555 <=== THIS IS WRONG, IT SHOULD BE THE DIALED NUMBER in the TO HEADER
18:17:34.870 ISDN.L2_FMT PRI 1 ==============================================
Any ideas?
I opened a ticked with Adtran and it turns out it was quite easy to fix this.
Add this command on your SIP Trunk (T01 or whatever you used as the identifier):
dial-string source to
From the manual:
dial-string source request-uri
dial-string source to
Syntax Description
request-uri -> Specifies the Request URI user field as the dialing string source.
to -> Specifies the To header field as the dialing string source.
I just solved a similar problem by buying a Session Border Controller to do SIP Header Manipulation.
I opened a ticked with Adtran and it turns out it was quite easy to fix this.
Add this command on your SIP Trunk (T01 or whatever you used as the identifier):
dial-string source to
From the manual:
dial-string source request-uri
dial-string source to
Syntax Description
request-uri -> Specifies the Request URI user field as the dialing string source.
to -> Specifies the To header field as the dialing string source.
Saved me last night with customer when switching over to SIP trunks from PRI. Thanks for sharing the solution!