Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4208
Views
0
Helpful
10
Replies

SIP FAILURE TO AUTHENTICATION

AndreAP
Level 1
Level 1

‎05-30-2018 01:04 PM - edited ‎03-17-2019 12:55 PM

Hello
Once again I ask my colleagues for help
my Router 2821 CME does not do the tricking in the sip trunk
below is the network and sip-au settings

 

sip-ua
 credentials username xxxxxx password  yyyyy realm xxx.xxx.xxx.2
 authentication username xxxxxx password  yyyyy realm xxx.xxx.xxx.2
 retry invite 2
 retry register 10
 retry options 1
 timers connect 100
 sip-server ipv4:xxx.xxx.xxx.2:5060


interface GigabitEthernet0/0
 ip address xxx.xxx.xxx.1 255.255.255.0
 ip nat inside
 ip virtual-reassembly
 duplex auto
 speed auto
!
interface GigabitEthernet0/1
 ip address dhcp
 ip nat outside
 ip virtual-reassembly
 duplex auto
 speed auto

 

my provider's trunk server uses Asterix

 

Thank you very much in advance

Labels:
0 Helpful
10 Replies 10

R0g22
Cisco Employee
Cisco Employee

‎05-30-2018 01:21 PM

So whats happening with this ? Trunk not registering ?

Enable "debug ccsip message" and remove the sip-ua config and re-add again. Share the logs here.
Also share an output for "show run | s voice service voip"

0 Helpful

AndreAP
Level 1
Level 1
In response to R0g22

‎05-30-2018 01:41 PM - edited ‎05-30-2018 01:54 PM

#show run | s voice service voip
 voice service voip
  allow-connections h323 to h323
  allow-connections h323 to sip
  allow-connections sip to h323
  allow-connections sip to sip
  no supplementary-service h450.3
  supplementary-service h450.12
  no supplementary-service sip moved-temporarily
  no supplementary-service sip refer
  fax protocol pass-through g711alaw
  h323
   ras timeout rrq  45
   ras retry rrq  30
   call start slow
   call preserve
  sip
   registrar server expires max 3600 min 3600
   no call service stop


#debug ccsip message

May 30 17:51:35.114: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:




INVITE sip:22222222@xxx.xxx.xxx.1;transport=TCP SIP/2.0
Via: SIP/2.0/TCP xxx.xxx.xxx.98:45406;branch=z9hG4bK-524287-1---01111e2ff2b8cb74;rport
Max-Forwards: 70
Contact: <sip:8190@xxx.xxx.xxx.98:45406;transport=tcp>
To: <sip:22222222@xxx.xxx.xxx.1;transport=TCP>
From: <sip:8190@xxx.xxx.xxx.1;transport=TCP>;tag=c8a77331
Call-ID: t-a0ExrW7xHaoJobH1lf5w..
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Content-Type: application/sdp
User-Agent: Zoiper rv2.8.87-mod
Allow-Events: presence, kpml, talk
Content-Length: 241

v=0
o=Zoiper 0 0 IN IP4 xxx.xxx.xxx.98
s=Zoiper
c=IN IP4 xxx.xxx.xxx.98
t=0 0
m=audio 36952 RTP/AVP 3 101 0 8
a=rtpmap:3 GSM/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=sendrecv

May 30 17:51:35.130: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:02122222222@xxx.xxx.xxx.2:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK81D6C
Remote-Party-ID: <sip:8190@xxx.xxx.0.159>;party=calling;screen=no;privacy=off
From: <sip:8190@xxx.xxx.0.159>;tag=17CF500-1A43
To: <sip:02122222222@xxx.xxx.xxx.2>
Date: Wed, 30 May 2018 17:51:35 gmt
Call-ID: EDBEF187-636811E8-81B5A1E9-217A665F@xxx.xxx.0.159
Supported: 100rel,timer,resource-priority,replaces
Min-SE:  1800
Cisco-Guid: 3988633911-1667764712-2175771113-561669727
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1527702695
Contact: <sip:8190@xxx.xxx.0.159:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 250

v=0
o=CiscoSystemsSIP-GW-UserAgent 2130 3736 IN IP4 xxx.xxx.0.159
s=SIP Call
c=IN IP4 xxx.xxx.0.159
t=0 0
m=audio 18278 RTP/AVP 0 101
c=IN IP4 xxx.xxx.0.159
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

May 30 17:51:35.130: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP xxx.xxx.xxx.98:45406;branch=z9hG4bK-524287-1---01111e2ff2b8cb74;rport
From: <sip:8190@xxx.xxx.xxx.1;transport=TCP>;tag=c8a77331
To: <sip:22222222@xxx.xxx.xxx.1;transport=TCP>
Date: Wed, 30 May 2018 17:51:35 gmt
Call-ID: t-a0ExrW7xHaoJobH1lf5w..
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 INVITE
Allow-Events: telephone-event
Content-Length: 0



May 30 17:51:35.158: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK81D6C;received=xxx.xxx.0.159;rport=53459
From: <sip:8190@xxx.xxx.0.159:5060>;tag=17CF500-1A43
To: <sip:02122222222@xxx.xxx.xxx.2>;tag=as662aa827
Call-ID: EDBEF187-636811E8-81B5A1E9-217A665F@xxx.xxx.0.159
CSeq: 101 INVITE
Server: SBC Gateway
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="480089dd"
Content-Length: 0


May 30 17:51:35.166: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:02122222222@xxx.xxx.xxx.2:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK81D6C
From: <sip:8190@xxx.xxx.0.159>;tag=17CF500-1A43
To: <sip:02122222222@xxx.xxx.xxx.2>;tag=as662aa827
Date: Wed, 30 May 2018 17:51:35 gmt
Call-ID: EDBEF187-636811E8-81B5A1E9-217A665F@xxx.xxx.0.159
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0



May 30 17:51:36.426: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP xxx.xxx.xxx.98:45406;branch=z9hG4bK-524287-1---01111e2ff2b8cb74;rport
From: <sip:8190@xxx.xxx.xxx.1;transport=TCP>;tag=c8a77331
To: <sip:22222222@xxx.xxx.xxx.1;transport=TCP>;tag=17CFA14-633
Date: Wed, 30 May 2018 17:51:35 gmt
Call-ID: t-a0ExrW7xHaoJobH1lf5w..
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 1 INVITE
Allow-Events: telephone-event
Reason: Q.850;cause=34
Content-Length: 0



May 30 17:51:36.742: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:22222222@xxx.xxx.xxx.1;transport=TCP SIP/2.0
Via: SIP/2.0/TCP xxx.xxx.xxx.98:45406;branch=z9hG4bK-524287-1---01111e2ff2b8cb74;rport
Max-Forwards: 70
To: <sip:22222222@xxx.xxx.xxx.1;transport=TCP>;tag=17CFA14-633
From: <sip:8190@xxx.xxx.xxx.1;transport=TCP>;tag=c8a77331
Call-ID: t-a0ExrW7xHaoJobH1lf5w..
CSeq: 1 ACK
Content-Length: 0

0 Helpful

AndreAP
Level 1
Level 1
In response to AndreAP

‎05-30-2018 01:56 PM

sorry, when I realized I had already posted the wrong debug already corrected

0 Helpful

R0g22
Cisco Employee
Cisco Employee
In response to AndreAP

‎05-30-2018 02:11 PM

Is this SIP trunk supposed to be registered to your ITSP before you can make calls ?
I see your ITSP sending a 401 with WWW header which is usually to challenge registrations. Since you made a call, sent an INVITE, your ITSP should have sent a 407 with Proxy-Authenticate header. Post getting 401, the CME sends a 503.

Do this -

sip-ua
registrar server ipv4:<ip of your ITSP registrar>

Your ITSP should have shared this information during circuit handoff. Post this check the trunk registration status with "show sip-ua register status". It should say "Yes".

0 Helpful

AndreAP
Level 1
Level 1
In response to R0g22

‎05-30-2018 02:27 PM

now gave this result

May 30 18:24:42.918: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:xxx.xxx.xxx.2:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK101E29
From: <sip:.*@xxx.xxx.xxx.2>;tag=19B49D0-704
To: <sip:.*@xxx.xxx.xxx.2>
Date: Wed, 30 May 2018 18:24:42 gmt
Call-ID: 234097DA-636D11E8-81BBA1E9-217A665F
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1527704682
CSeq: 3 REGISTER
Contact: <sip:.*@xxx.xxx.0.159:5060>
Expires:  3600
Content-Length: 0



May 30 18:24:42.922: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:xxx.xxx.xxx.2:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK11C5F
From: <sip:8180@xxx.xxx.xxx.2>;tag=19B49D4-10A5
To: <sip:8180@xxx.xxx.xxx.2>
Date: Wed, 30 May 2018 18:24:42 gmt
Call-ID: 2341349B-636D11E8-81BCA1E9-217A665F
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1527704682
CSeq: 3 REGISTER
Contact: <sip:8180@xxx.xxx.0.159:5060>
Expires:  3600
Content-Length: 0



May 30 18:24:42.922: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:xxx.xxx.xxx.2:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK1214F4
From: <sip:8181@xxx.xxx.xxx.2>;tag=19B49D4-6BA
To: <sip:8181@xxx.xxx.xxx.2>
Date: Wed, 30 May 2018 18:24:42 gmt
Call-ID: 2341349B-636D11E8-81BDA1E9-217A665F
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1527704682
CSeq: 3 REGISTER
Contact: <sip:8181@xxx.xxx.0.159:5060>
Expires:  3600
Content-Length: 0



May 30 18:24:42.926: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:xxx.xxx.xxx.2:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK131227
From: <sip:8182@xxx.xxx.xxx.2>;tag=19B49D8-FD8
To: <sip:8182@xxx.xxx.xxx.2>
Date: Wed, 30 May 2018 18:24:42 gmt
Call-ID: 2341D0C3-636D11E8-81BEA1E9-217A665F
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1527704682
CSeq: 3 REGISTER
Contact: <sip:8182@xxx.xxx.0.159:5060>
Expires:  3600
Content-Length: 0



May 30 18:24:42.930: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:xxx.xxx.xxx.2:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK142561
From: <sip:8183@xxx.xxx.xxx.2>;tag=19B49D8-E06
To: <sip:8183@xxx.xxx.xxx.2>
Date: Wed, 30 May 2018 18:24:42 gmt
Call-ID: 2341D0C3-636D11E8-81BFA1E9-217A665F
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1527704682
CSeq: 3 REGISTER
Contact: <sip:8183@xxx.xxx.0.159:5060>
Expires:  3600
Content-Length: 0



May 30 18:24:42.930: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:xxx.xxx.xxx.2:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK15AE7
From: <sip:8190@xxx.xxx.xxx.2>;tag=19B49D8-208C
To: <sip:8190@xxx.xxx.xxx.2>
Date: Wed, 30 May 2018 18:24:42 gmt
Call-ID: 23426CEB-636D11E8-81C0A1E9-217A665F
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1527704682
CSeq: 3 REGISTER
Contact: <sip:8190@xxx.xxx.0.159:5060>
Expires:  3600
Content-Length: 0



May 30 18:24:42.930: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:xxx.xxx.xxx.2:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK1625CE
From: <sip:usisip@xxx.xxx.xxx.2>;tag=19B49D8-5B9
To: <sip:usisip@xxx.xxx.xxx.2>
Date: Wed, 30 May 2018 18:24:42 gmt
Call-ID: 23426CEB-636D11E8-81C1A1E9-217A665F
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1527704682
CSeq: 3 REGISTER
Contact: <sip:usisip@xxx.xxx.0.159:5060>
Expires:  3600
Content-Length: 0



May 30 18:24:42.946: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK101E29;received=xxx.xxx.0.159;rport=56057
From: <sip:.*@xxx.xxx.xxx.2>;tag=19B49D0-704
To: <sip:.*@xxx.xxx.xxx.2>;tag=as27b556e5
Call-ID: 234097DA-636D11E8-81BBA1E9-217A665F
CSeq: 3 REGISTER
Server: SBC Gateway
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="6cabd07b"
Content-Length: 0



May 30 18:24:42.954: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK11C5F;received=xxx.xxx.0.159;rport=56057
From: <sip:8180@xxx.xxx.xxx.2>;tag=19B49D4-10A5
To: <sip:8180@xxx.xxx.xxx.2>;tag=as085356bb
Call-ID: 2341349B-636D11E8-81BCA1E9-217A665F
CSeq: 3 REGISTER
Server: SBC Gateway
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="6ef3b975"
Content-Length: 0



May 30 18:24:42.954: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK1214F4;received=xxx.xxx.0.159;rport=56057
From: <sip:8181@xxx.xxx.xxx.2>;tag=19B49D4-6BA
To: <sip:8181@xxx.xxx.xxx.2>;tag=as6e98e588
Call-ID: 2341349B-636D11E8-81BDA1E9-217A665F
CSeq: 3 REGISTER
Server: SBC Gateway
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="79a16ec1"
Content-Length: 0



May 30 18:24:42.958: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK131227;received=xxx.xxx.0.159;rport=56057
From: <sip:8182@xxx.xxx.xxx.2>;tag=19B49D8-FD8
To: <sip:8182@xxx.xxx.xxx.2>;tag=as5cd36ea0
Call-ID: 2341D0C3-636D11E8-81BEA1E9-217A665F
CSeq: 3 REGISTER
Server: SBC Gateway
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="6897fdfc"
Content-Length: 0



May 30 18:24:42.962: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK142561;received=xxx.xxx.0.159;rport=56057
From: <sip:8183@xxx.xxx.xxx.2>;tag=19B49D8-E06
To: <sip:8183@xxx.xxx.xxx.2>;tag=as0cb5140b
Call-ID: 2341D0C3-636D11E8-81BFA1E9-217A665F
CSeq: 3 REGISTER
Server: SBC Gateway
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="0e6e43ec"
Content-Length: 0



May 30 18:24:42.962: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK15AE7;received=xxx.xxx.0.159;rport=56057
From: <sip:8190@xxx.xxx.xxx.2>;tag=19B49D8-208C
To: <sip:8190@xxx.xxx.xxx.2>;tag=as1405aa1a
Call-ID: 23426CEB-636D11E8-81C0A1E9-217A665F
CSeq: 3 REGISTER
Server: SBC Gateway
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="281e7d9d"
Content-Length: 0



May 30 18:24:42.962: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xxx.xxx.0.159:5060;branch=z9hG4bK1625CE;received=xxx.xxx.0.159;rport=56057
From: <sip:usisip@xxx.xxx.xxx.2>;tag=19B49D8-5B9
To: <sip:usisip@xxx.xxx.xxx.2>;tag=as2d5ed740
Call-ID: 23426CEB-636D11E8-81C1A1E9-217A665F
CSeq: 3 REGISTER
Server: SBC Gateway
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="7d2da5ee"
Content-Length: 0


show sip-ua register status
Line          peer           expires(sec)  registered
============  =============  ============  ===========
.*            75               120           no
usisip        -1               120           no
8180          10               120           no
8181          15               120           no
8182          20001            120           no
8183          40001            120           no
8190          40002            120           no

0 Helpful

R0g22
Cisco Employee
Cisco Employee
In response to AndreAP

‎05-31-2018 01:19 AM

These are not complete logs. After we get 401 from ITSP, I don't see any new REGISTER messages going out. Can you take the logs in a text file please ?

0 Helpful

AndreAP
Level 1
Level 1
In response to R0g22

‎05-31-2018 08:02 AM

is attached

Preview file
7 KB
0 Helpful

AndreAP
Level 1
Level 1
In response to R0g22

‎05-30-2018 02:38 PM - edited ‎05-30-2018 08:19 PM

.

0 Helpful

AndreAP
Level 1
Level 1

‎05-30-2018 03:00 PM - edited ‎05-30-2018 08:24 PM

sorry for several replies was showing error for me

0 Helpful

AndreAP
Level 1
Level 1

‎05-30-2018 03:05 PM - edited ‎05-30-2018 08:21 PM

.

0 Helpful
Customers Also Viewed These Support Documents