Adtran
Help
The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Anonymous
Not applicable
‎07-11-2012 01:40 PM

Cannot Dial out via Sip Trunk Adtran 7100

Jump to solution

Does any one have any source that can help me learn how to read sip message?  Like some sort of on line training?

Ok.  Here's the problem.  I've setup the sip trunk.

show sip trunk register -

Trk       Identity       Reg'd  Grant  Expires Success Failed Requests Chal Roll

--- -------------------- ----- ------- ------- ------- ------ -------- ---- ----

T06           xxxyyyzzzz   Yes    3600     970      19      1       37   18    0

Total Displayed: 1

I've check the dialing plan.  It looks good to me.

I can't dial out....

I made a phone call while running debug..

debug ip sip stack message

Here is the result

13:33:55.010 SIP.STACK MSG         From: User Name <sip:114@192.168.152.254:5060>;tag=a0a55edb0e90d69

13:33:55.010 SIP.STACK MSG         To: 9xxxxxxx <sip:9xxxxxxx@192.168.152.254:5060>

13:33:55.010 SIP.STACK MSG         CSeq: 1219762431 INVITE

13:33:55.011 SIP.STACK MSG         Supported: 100rel

13:33:55.011 SIP.STACK MSG         Supported: timer

13:33:55.011 SIP.STACK MSG         Allow: SUBSCRIBE, NOTIFY, REFER, OPTIONS, MESSAGE, INVITE, ACK, CANCEL, BYE, INFO

13:33:55.011 SIP.STACK MSG         Content-Type: application/sdp

13:33:55.011 SIP.STACK MSG         Contact: User Name <sip:114@192.168.152.52:5060>

13:33:55.011 SIP.STACK MSG         Supported: replaces

13:33:55.012 SIP.STACK MSG         User-Agent: Adtran-SIP-IP712/v1.3.15

13:33:55.012 SIP.STACK MSG

13:33:55.012 SIP.STACK MSG         v=0

13:33:55.012 SIP.STACK MSG         o=MxSIP 0 2078132939 IN IP4 192.168.152.52

13:33:55.012 SIP.STACK MSG         s=SIP Call

13:33:55.012 SIP.STACK MSG         c=IN IP4 192.168.152.52

13:33:55.013 SIP.STACK MSG         t=0 0

13:33:55.013 SIP.STACK MSG         m=audio 3000 RTP/AVP 0 18 103 102 107 104 105 101 8

13:33:55.013 SIP.STACK MSG         a=rtpmap:0 PCMU/8000

13:33:55.013 SIP.STACK MSG         a=rtpmap:18 G729/8000

13:33:55.013 SIP.STACK MSG         a=rtpmap:103 BV16/8000

13:33:55.013 SIP.STACK MSG         a=rtpmap:102 BV32/16000

13:33:55.014 SIP.STACK MSG         a=rtpmap:107 L16/16000

13:33:55.014 SIP.STACK MSG         a=rtpmap:104 PCMU/16000

13:33:55.014 SIP.STACK MSG         a=rtpmap:105 PCMA/16000

13:33:55.014 SIP.STACK MSG         a=rtpmap:101 telephone-event/8000

13:33:55.014 SIP.STACK MSG         a=rtpmap:8 PCMA/8000

13:33:55.014 SIP.STACK MSG         a=fmtp:101 0-15

13:33:55.015 SIP.STACK MSG         a=ptime:20

13:33:55.015 SIP.STACK MSG         a=sendrecv

13:33:55.015 SIP.STACK MSG         a=silenceSupp:off - - - -

13:33:55.015 SIP.STACK MSG

13:33:55.019 SIP.STACK MSG     Tx: UDP src=192.168.152.254:5060 dst=192.168.152.52:5060

13:33:55.019 SIP.STACK MSG         SIP/2.0 100 Trying

13:33:55.019 SIP.STACK MSG         From: User Name <sip:114@192.168.152.254:5060>;tag=a0a55edb0e90d69

13:33:55.020 SIP.STACK MSG         To: 9xxxxxxx <sip:9xxxxxxx@192.168.152.254:5060>

13:33:55.020 SIP.STACK MSG         Call-ID: d56e9dd9a7b4432ccee94235bc50d108@192.168.152.52

13:33:55.020 SIP.STACK MSG         CSeq: 1219762431 INVITE

13:33:55.020 SIP.STACK MSG         Via: SIP/2.0/UDP 192.168.152.52:5060;branch=z9hG4bK6508d2848

13:33:55.020 SIP.STACK MSG         Contact: <sip:192.168.152.254:5060;transport=UDP>

13:33:55.020 SIP.STACK MSG         Supported: 100rel,replaces

13:33:55.021 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

13:33:55.021 SIP.STACK MSG         User-Agent: ADTRAN_NetVanta_7100/R10.2.M.5.E

13:33:55.021 SIP.STACK MSG         Content-Length: 0

13:33:55.021 SIP.STACK MSG

13:33:55.028 SIP.STACK MSG     Tx: UDP src=192.168.152.254:5060 dst=192.168.152.51:5060

13:33:55.028 SIP.STACK MSG         NOTIFY sip:113@192.168.152.51:5060;transport=udp SIP/2.0

13:33:55.028 SIP.STACK MSG         From: 201 <sip:201@192.168.152.254>;tag=5232620-18ad1bc2-13c4-f043-fae2d65b-f043

13:33:55.028 SIP.STACK MSG         To: User 2 <sip:113@192.168.152.254:5060>;tag=638ecad65d22872

13:33:55.029 SIP.STACK MSG         Call-ID: 793091b8b9b653ce206786146f1ca039@192.168.152.51

13:33:55.029 SIP.STACK MSG         CSeq: 2 NOTIFY

13:33:55.029 SIP.STACK MSG         Via: SIP/2.0/UDP 192.168.152.254:5060;branch=z9hG4bK-f05b-3aae55d-72c42037

13:33:55.029 SIP.STACK MSG         Subscription-State: active

13:33:55.029 SIP.STACK MSG         Event: dialog

13:33:55.029 SIP.STACK MSG         Max-Forwards: 70

13:33:55.030 SIP.STACK MSG         Supported: 100rel,replaces

13:33:55.030 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

13:33:55.030 SIP.STACK MSG         User-Agent: ADTRAN_NetVanta_7100/R10.2.M.5.E

13:33:55.030 SIP.STACK MSG         Contact: <sip:201@192.168.152.254>

13:33:55.030 SIP.STACK MSG         Content-Type: multipart/related;boundary=uBd;type="application/rlmi+xml"

13:33:55.031 SIP.STACK MSG         Content-Length: 745

13:33:55.031 SIP.STACK MSG

13:33:55.031 SIP.STACK MSG         --uBd

13:33:55.031 SIP.STACK MSG         c:application/rlmi+xml

13:33:55.031 SIP.STACK MSG         l:296

13:33:55.031 SIP.STACK MSG         Content-ID:<F59@192.168.152.254>

13:33:55.031 SIP.STACK MSG

13:33:55.032 SIP.STACK MSG         <?xml version="1.0" encoding="UTF-8"?><list xmlns="urn:ietf:params:xml:ns:rlmi" version="1" fullState="false" uri="sip:201@192.168.152.254"><resource uri="s

ip:114@192.168.152.254"><name>114</name><instance id="9FD" state="active" cid="51C@192.168.152.254"></instance></resource></list>

13:33:55.032 SIP.STACK MSG         --uBd

13:33:55.032 SIP.STACK MSG         c:application/dialog-info+xml

13:33:55.032 SIP.STACK MSG         l:305

13:33:55.032 SIP.STACK MSG         Content-ID:<51C@192.168.152.254>

13:33:55.032 SIP.STACK MSG

13:33:55.033 SIP.STACK MSG         <?xml version="1.0" encoding="UTF-8"?><dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="1" state="full" entity="114@192.168.152.254"><dialog

id="91F"><state>confirmed</state><local><identity display="User Name">sip:114@192.168.152.254</identity></local></dialog></dialog-info>

13:33:55.033 SIP.STACK MSG         --uBd--

13:33:55.033 SIP.STACK MSG

13:33:55.042 SIP.STACK MSG     Tx: UDP src=1.1.1.1:5060 dst=2.2.2.2:5060

13:33:55.042 SIP.STACK MSG         INVITE sip:xxxxxxx@sip.provider.net:5060 SIP/2.0

13:33:55.043 SIP.STACK MSG         From: "User Name" <sip:114@sip.provider.net:5060;transport=UDP>;tag=5232de0-18ad1bc2-13c4-f05b-a6448d14-f05b

13:33:55.043 SIP.STACK MSG         To: <sip:xxxxxxx@sip.provider.net:5060>

13:33:55.043 SIP.STACK MSG         Call-ID: 52b7de8-18ad1bc2-13c4-f05b-deacc7f0-f05b@sip.provider.net

13:33:55.043 SIP.STACK MSG         CSeq: 1 INVITE

13:33:55.043 SIP.STACK MSG         Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK-f05b-3aae56b-e5ecbc

13:33:55.043 SIP.STACK MSG         Max-Forwards: 70

13:33:55.044 SIP.STACK MSG         Supported: 100rel,replaces

13:33:55.044 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

13:33:55.044 SIP.STACK MSG         User-Agent: ADTRAN_NetVanta_7100/R10.2.M.5.E

13:33:55.044 SIP.STACK MSG         Contact: <sip:114@1.1.1.1:5060;transport=UDP>

13:33:55.044 SIP.STACK MSG         Content-Type: application/sdp

13:33:55.044 SIP.STACK MSG         Content-Length: 292

13:33:55.045 SIP.STACK MSG

13:33:55.045 SIP.STACK MSG         v=0

13:33:55.045 SIP.STACK MSG         o=MxSIP 0 2078132939 IN IP4 1.1.1.1

13:33:55.045 SIP.STACK MSG         s=SIP Call

13:33:55.045 SIP.STACK MSG         c=IN IP4 1.1.1.1

13:33:55.045 SIP.STACK MSG         t=0 0

13:33:55.045 SIP.STACK MSG         m=audio 50016 RTP/AVP 0 18 101

13:33:55.046 SIP.STACK MSG         a=ptime:20

13:33:55.046 SIP.STACK MSG         a=sendrecv

13:33:55.046 SIP.STACK MSG         a=silenceSupp:off - - - -

13:33:55.046 SIP.STACK MSG         a=rtpmap:0 PCMU/8000

13:33:55.046 SIP.STACK MSG         a=rtpmap:18 G729/8000

13:33:55.046 SIP.STACK MSG         a=fmtp:18 annexb=no

13:33:55.047 SIP.STACK MSG         a=rtpmap:101 telephone-event/8000

13:33:55.047 SIP.STACK MSG         a=fmtp:101 0-15

13:33:55.047 SIP.STACK MSG

13:33:55.073 SIP.STACK MSG     Rx: UDP src=2.2.2.2:5060 dst=1.1.1.1:5060

13:33:55.073 SIP.STACK MSG         SIP/2.0 100 Trying

13:33:55.074 SIP.STACK MSG         From: "User Name" <sip:114@2.2.2.2:5060;transport=UDP>;tag=5232de0-18ad1bc2-13c4-f05b-a6448d14-f05b

13:33:55.074 SIP.STACK MSG         To: <sip:xxxxxxx@sip.provider.net:5060>

13:33:55.074 SIP.STACK MSG         Call-ID: 52b7de8-18ad1bc2-13c4-f05b-deacc7f0-f05b@sip.provider.net

13:33:55.074 SIP.STACK MSG         CSeq: 1 INVITE

13:33:55.074 SIP.STACK MSG         Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK-f05b-3aae56b-e5ecbc

13:33:55.074 SIP.STACK MSG

13:33:55.079 SIP.STACK MSG     Rx: UDP src=2.2.2.2:5060 dst=1.1.1.1:5060

13:33:55.079 SIP.STACK MSG         SIP/2.0 403 From: URI not recognized

13:33:55.079 SIP.STACK MSG         From: "User Name" <sip:114@2.2.2.2:5060;transport=UDP>;tag=5232de0-18ad1bc2-13c4-f05b-a6448d14-f05b

13:33:55.079 SIP.STACK MSG         To: <sip:xxxxxxx@sip.provider.net:5060>;tag=SDenpge99-10.45.0.40+1+0+56a85fb5

13:33:55.079 SIP.STACK MSG         Call-ID: 52b7de8-18ad1bc2-13c4-f05b-deacc7f0-f05b@sip.provider.net

13:33:55.080 SIP.STACK MSG         CSeq: 1 INVITE

13:33:55.080 SIP.STACK MSG         Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK-f05b-3aae56b-e5ecbc

13:33:55.080 SIP.STACK MSG         Server: DC-SIP/2.0

13:33:55.080 SIP.STACK MSG         Organization: Bestline

13:33:55.080 SIP.STACK MSG         Content-Length: 0

13:33:55.080 SIP.STACK MSG

13:33:55.083 SIP.STACK MSG     Tx: UDP src=1.1.1.1:5060 dst=2.2.2.2:5060

13:33:55.083 SIP.STACK MSG         ACK sip:xxxxxxx@sip.provider.net:5060;transport=UDP SIP/2.0

13:33:55.083 SIP.STACK MSG         From: "User Name" <sip:114@sip.provider.net:5060;transport=UDP>;tag=5232de0-18ad1bc2-13c4-f05b-a6448d14-f05b

13:33:55.083 SIP.STACK MSG         To: <sip:xxxxxxx@sip.provider.net:5060>;tag=SDenpge99-10.45.0.40+1+0+56a85fb5

13:33:55.084 SIP.STACK MSG         Call-ID: 52b7de8-18ad1bc2-13c4-f05b-deacc7f0-f05b@sip.provider.net

13:33:55.084 SIP.STACK MSG         CSeq: 1 ACK

13:33:55.084 SIP.STACK MSG         Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK-f05b-3aae56b-e5ecbc

13:33:55.084 SIP.STACK MSG         Max-Forwards: 70

13:33:55.084 SIP.STACK MSG         Supported: 100rel,replaces

13:33:55.084 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

13:33:55.085 SIP.STACK MSG         User-Agent: ADTRAN_NetVanta_7100/R10.2.M.5.E

13:33:55.085 SIP.STACK MSG         Contact: <sip:114@1.1.1.1:5060;transport=UDP>

13:33:55.085 SIP.STACK MSG         Content-Length: 0

13:33:55.085 SIP.STACK MSG

13:33:55.087 SIP.STACK MSG     Tx: UDP src=192.168.152.254:5060 dst=192.168.152.52:5060

13:33:55.088 SIP.STACK MSG         SIP/2.0 403 Forbidden

13:33:55.088 SIP.STACK MSG         From: User Name <sip:114@192.168.152.254:5060>;tag=a0a55edb0e90d69

13:33:55.088 SIP.STACK MSG         To: 9xxxxxxx <sip:9xxxxxxx@192.168.152.254:5060>;tag=5232a00-18ad1bc2-13c4-f05b-92a94f53-f05b

13:33:55.088 SIP.STACK MSG         Call-ID: d56e9dd9a7b4432ccee94235bc50d108@192.168.152.52

13:33:55.088 SIP.STACK MSG         CSeq: 1219762431 INVITE

13:33:55.089 SIP.STACK MSG         Via: SIP/2.0/UDP 192.168.152.52:5060;branch=z9hG4bK6508d2848

13:33:55.089 SIP.STACK MSG         Supported: 100rel,replaces

13:33:55.089 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

13:33:55.089 SIP.STACK MSG         User-Agent: ADTRAN_NetVanta_7100/R10.2.M.5.E

13:33:55.089 SIP.STACK MSG         Content-Length: 0

13:33:55.089 SIP.STACK MSG

13:33:55.096 SIP.STACK MSG     Rx: UDP src=192.168.152.51:5060 dst=192.168.152.254:5060

13:33:55.096 SIP.STACK MSG         SIP/2.0 200 OK

13:33:55.097 SIP.STACK MSG         Call-ID: 793091b8b9b653ce206786146f1ca039@192.168.152.51

13:33:55.097 SIP.STACK MSG         CSeq: 2 NOTIFY

13:33:55.097 SIP.STACK MSG         From: 201 <sip:201@192.168.152.254>;tag=5232620-18ad1bc2-13c4-f043-fae2d65b-f043

13:33:55.097 SIP.STACK MSG         To: User 2 <sip:113@192.168.152.254:5060>;tag=638ecad65d22872

13:33:55.097 SIP.STACK MSG         Via: SIP/2.0/UDP 192.168.152.254:5060;branch=z9hG4bK-f05b-3aae55d-72c42037

13:33:55.097 SIP.STACK MSG         Content-Length: 0

13:33:55.098 SIP.STACK MSG         Contact: User 2 <sip:113@192.168.152.51:5060;transport=udp>

13:33:55.098 SIP.STACK MSG         Supported: replaces

13:33:55.098 SIP.STACK MSG         User-Agent: Adtran-SIP-IP706/v1.3.13

13:33:55.098 SIP.STACK MSG

13:33:55.150 SIP.STACK MSG     Rx: UDP src=192.168.152.52:5060 dst=192.168.152.254:5060

13:33:55.150 SIP.STACK MSG         ACK sip:192.168.152.254:5060;transport=UDP SIP/2.0

13:33:55.150 SIP.STACK MSG         Max-Forwards: 70

13:33:55.151 SIP.STACK MSG         Content-Length: 0

13:33:55.151 SIP.STACK MSG         Via: SIP/2.0/UDP 192.168.152.52:5060;branch=z9hG4bK6508d2848

13:33:55.151 SIP.STACK MSG         Call-ID: d56e9dd9a7b4432ccee94235bc50d108@192.168.152.52

13:33:55.151 SIP.STACK MSG         From: User Name <sip:114@192.168.152.254:5060>;tag=a0a55edb0e90d69

13:33:55.151 SIP.STACK MSG         To: 9xxxxxxx <sip:9xxxxxxx@192.168.152.254:5060>;tag=5232a00-18ad1bc2-13c4-f05b-92a94f53-f05b

13:33:55.152 SIP.STACK MSG         CSeq: 1219762431 ACK

13:33:55.152 SIP.STACK MSG         User-Agent: Adtran-SIP-IP712/v1.3.15

13:33:55.152 SIP.STACK MSG

13:33:57.033 SIP.STACK MSG     Tx: UDP src=192.168.152.254:5060 dst=192.168.152.51:5060

13:33:57.034 SIP.STACK MSG         NOTIFY sip:113@192.168.152.51:5060;transport=udp SIP/2.0

13:33:57.034 SIP.STACK MSG         From: 201 <sip:201@192.168.152.254>;tag=5232620-18ad1bc2-13c4-f043-fae2d65b-f043

13:33:57.034 SIP.STACK MSG         To: User 2 <sip:113@192.168.152.254:5060>;tag=638ecad65d22872

13:33:57.034 SIP.STACK MSG         Call-ID: 793091b8b9b653ce206786146f1ca039@192.168.152.51

13:33:57.034 SIP.STACK MSG         CSeq: 3 NOTIFY

13:33:57.034 SIP.STACK MSG         Via: SIP/2.0/UDP 192.168.152.254:5060;branch=z9hG4bK-f05d-3aaed31-4d5709a2

13:33:57.034 SIP.STACK MSG         Subscription-State: active

13:33:57.035 SIP.STACK MSG         Event: dialog

13:33:57.035 SIP.STACK MSG         Max-Forwards: 70

13:33:57.035 SIP.STACK MSG         Supported: 100rel,replaces

13:33:57.035 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

13:33:57.035 SIP.STACK MSG         User-Agent: ADTRAN_NetVanta_7100/R10.2.M.5.E

13:33:57.036 SIP.STACK MSG         Contact: <sip:201@192.168.152.254>

13:33:57.036 SIP.STACK MSG         Content-Type: multipart/related;boundary=uBd;type="application/rlmi+xml"

13:33:57.036 SIP.STACK MSG         Content-Length: 746

13:33:57.036 SIP.STACK MSG

13:33:57.036 SIP.STACK MSG         --uBd

13:33:57.036 SIP.STACK MSG         c:application/rlmi+xml

13:33:57.036 SIP.STACK MSG         l:296

13:33:57.037 SIP.STACK MSG         Content-ID:<97E@192.168.152.254>

13:33:57.037 SIP.STACK MSG

13:33:57.037 SIP.STACK MSG         <?xml version="1.0" encoding="UTF-8"?><list xmlns="urn:ietf:params:xml:ns:rlmi" version="2" fullState="false" uri="sip:201@192.168.152.254"><resource uri="s

ip:114@192.168.152.254"><name>114</name><instance id="BE3" state="active" cid="39D@192.168.152.254"></instance></resource></list>

13:33:57.037 SIP.STACK MSG         --uBd

13:33:57.037 SIP.STACK MSG         c:application/dialog-info+xml

13:33:57.037 SIP.STACK MSG         l:306

13:33:57.038 SIP.STACK MSG         Content-ID:<39D@192.168.152.254>

13:33:57.038 SIP.STACK MSG

13:33:57.038 SIP.STACK MSG         <?xml version="1.0" encoding="UTF-8"?><dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="2" state="full" entity="114@192.168.152.254"><dialog

id="453"><state>terminated</state><local><identity display="User Name">sip:114@192.168.152.254</identity></local></dialog></dialog-info>

13:33:57.038 SIP.STACK MSG         --uBd--

13:33:57.038 SIP.STACK MSG

13:33:57.102 SIP.STACK MSG     Rx: UDP src=192.168.152.51:5060 dst=192.168.152.254:5060

13:33:57.102 SIP.STACK MSG         SIP/2.0 200 OK

13:33:57.102 SIP.STACK MSG         Call-ID: 793091b8b9b653ce206786146f1ca039@192.168.152.51

13:33:57.102 SIP.STACK MSG         CSeq: 3 NOTIFY

13:33:57.103 SIP.STACK MSG         From: 201 <sip:201@192.168.152.254>;tag=5232620-18ad1bc2-13c4-f043-fae2d65b-f043

13:33:57.103 SIP.STACK MSG         To: User 2 <sip:113@192.168.152.254:5060>;tag=638ecad65d22872

13:33:57.103 SIP.STACK MSG         Via: SIP/2.0/UDP 192.168.152.254:5060;branch=z9hG4bK-f05d-3aaed31-4d5709a2

13:33:57.103 SIP.STACK MSG         Content-Length: 0

13:33:57.104 SIP.STACK MSG         Contact: User 2 <sip:113@192.168.152.51:5060;transport=udp>

13:33:57.104 SIP.STACK MSG         Supported: replaces

13:33:57.104 SIP.STACK MSG         User-Agent: Adtran-SIP-IP706/v1.3.13

13:33:57.105 SIP.STACK MSG

Message was edited by: matt - removed public IPs, name, and public phone numbers

0 Kudos
Reply
1 Solution

Accepted Solutions
Anonymous
Not applicable
‎07-11-2012 03:40 PM

Re: Cannot Dial out via Sip Trunk Adtran 7100

Jump to solution

Dear Touristsis,

I think that you can solve your problem with the match-ani command under your SIP trunks. Example below:

match ani "$" substitute "XXXXXXXX"

With that command you are changing your extension number from where the call comes and change it with your ITSP assigned number.

Hope this helps,

View solution in original post

0 Kudos
Reply
4 Replies
Anonymous
Not applicable
‎07-11-2012 01:44 PM

Re: Cannot Dial out via Sip Trunk Adtran 7100

Jump to solution

I've found the problem while reading that debug again.  I was broadcasting my extension number 114 instead of the ten digit phone number to the ITSP. 
Under Station, User Accounts, Voip, I've added a new sip identity that ties to the the trunks.

Does any on know a way around this?  Do we have to do this to every phones? 
On most installs I've done, I just have to register the sip trunks one time and call it a day. 
I can't imagine having to do this on every phone.

0 Kudos
Accept as Solution Reply
Anonymous
Not applicable
‎07-11-2012 03:40 PM

Re: Cannot Dial out via Sip Trunk Adtran 7100

Jump to solution

Dear Touristsis,

I think that you can solve your problem with the match-ani command under your SIP trunks. Example below:

match ani "$" substitute "XXXXXXXX"

With that command you are changing your extension number from where the call comes and change it with your ITSP assigned number.

Hope this helps,

0 Kudos
Reply
Anonymous
Not applicable
‎07-11-2012 04:05 PM

Re: Cannot Dial out via Sip Trunk Adtran 7100

Jump to solution

Thanks for the PROMP REPLY.  That did the trick!

0 Kudos
Accept as Solution Reply
Anonymous
Not applicable
‎08-07-2012 10:22 AM

Re: Cannot Dial out via Sip Trunk Adtran 7100

Jump to solution

We just published a new guide that details which configuration options are used to determine outbound caller ID:

Thanks,

Matt

Accept as Solution Reply