02-18-2013 07:27 AM - edited 03-16-2019 03:47 PM
Hello,
The scenario in which we find is the following:
SCENARIO:
1.- UC560 version
UC500 Software (UC500-ADVIPSERVICESK9-M), Version 15.1(2)T4, RELEASE SOFTWARE (fc1)
2.- SIP Phones UC560
show sip-ua register status
Line peer expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
0* 102 109 no # SIP phone
104 4 109 no # SIP phone
150 40004 133 no # SIP phone
170 40003 132 no # SIP phone
171 40002 91 no # SIP phone
180 40001 19 no # SIP phone
2508205196 -1 1366 yes # SIP TRUNK
5... 20001 109 no # SIP phone
520 20075 109 no # SIP phone
3.- Troncal SIP
show sip-ua register status
Line peer expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
0* 102 109 no # SIP phone
104 4 109 no # SIP phone
150 40004 133 no # SIP phone
170 40003 132 no # SIP phone
171 40002 91 no # SIP phone
180 40001 19 no # SIP phone
2508205196 -1 1366 yes # SIP TRUNK
5... 20001 109 no # SIP phone
520 20075 109 no # SIP phone
PROBLEMA
All SIP phones try to register with the SIP provider. The SIP trunk provider when it receives more than 10 attempts failed records of UC560 IP bans. The unit is operating as a SIP proxy and forward REGISTER requests from SIP phones to SIP trunk, which as soon as you to realize more than 10 attempts the UC560 IP is in the blacklist and can not make calls.
Below are some examples of debugging,
# debug ccsip messages
Sent:
REGISTER sip:sip.netelip.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK82FC76C
From: <sip:520@sip.netelip.com>;tag=134DA8A8-1070
To: <sip:520@sip.netelip.com>
Date: Mon, 18 Feb 2013 14:04:52 GMT
Call-ID: E797F5B-761911E2-8006B1F0-399A5411
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 1
Timestamp: 1361196292
CSeq: 3591 REGISTER
Contact: <sip:520@192.168.1.9:5060>
Expires: 3600
Supported: path
Content-Length: 0
Sent:
REGISTER sip:sip.netelip.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK82FD226A
From: <sip:0*@sip.netelip.com>;tag=134DA8B0-4FFB
To: <sip:0*@sip.netelip.com>
Date: Mon, 18 Feb 2013 14:04:52 GMT
Call-ID: D9056E8-761911E2-8002B1F0-399A5411
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 1
Timestamp: 1361196292
CSeq: 3589 REGISTER
Contact: <sip:0*@192.168.1.9:5060>
Expires: 3600
Supported: path
Content-Length: 0
Sent:
REGISTER sip:sip.netelip.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK82FE5AA
From: <sip:104@sip.netelip.com>;tag=134DA8EC-1D52
To: <sip:104@sip.netelip.com>
Date: Mon, 18 Feb 2013 14:04:52 GMT
Call-ID: DAF79A8-761911E2-8003B1F0-399A5411
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 1
Timestamp: 1361196292
CSeq: 3591 REGISTER
Contact: <sip:104@192.168.1.9:5060>
Expires: 3600
Supported: path
Content-Length: 0
Previous attempts result in authentication failure and the IP ban UC560.
Received:
SIP/2.0 403 Forbidden (Bad auth)
Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK82FFB0;received=217.125.71.164;rport=41626
From: <sip:520@sip.netelip.com>;tag=134DA8A8-1070
To: <sip:520@sip.netelip.com>;tag=as0787db9c
Call-ID: E797F5B-761911E2-8006B1F0-399A5411
CSeq: 3592 REGISTER
Server: Netelip
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
Received:
SIP/2.0 403 Forbidden (Bad auth)
Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK8300198C;received=217.125.71.164;rport=41626
From: <sip:0*@sip.netelip.com>;tag=134DA8B0-4FFB
To: <sip:0*@sip.netelip.com>;tag=as1cb35a3c
Call-ID: D9056E8-761911E2-8002B1F0-399A5411
CSeq: 3590 REGISTER
Server: Netelip
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
Received:
SIP/2.0 403 Forbidden (Bad auth)
Via: SIP/2.0/UDP 192.168.1.9:5060;branch=z9hG4bK83012088;received=217.125.71.164;rport=41626
From: <sip:104@sip.netelip.com>;tag=134DA8EC-1D52
To: <sip:104@sip.netelip.com>;tag=as139a9b22
Call-ID: DAF79A8-761911E2-8003B1F0-399A5411
CSeq: 3592 REGISTER
Server: Netelip
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
QUESTION
How can we prevent you to realize SIP phone registration attempts against SIP trunk?, And thus prevent the IP provider's IP ban the user the UC560.
Solved! Go to Solution.
02-18-2013 07:31 AM
Hi
This is very normal
Add the no-reg primary into ALL the ephone-dns
Also you have to do the same for the rest
Dial peers , etc
Example:
ephone-dn 1 dual-line
number 0900 no-reg primary
dial-peer voice 20 pots
no sip-register
02-18-2013 07:31 AM
Hi
This is very normal
Add the no-reg primary into ALL the ephone-dns
Also you have to do the same for the rest
Dial peers , etc
Example:
ephone-dn 1 dual-line
number 0900 no-reg primary
dial-peer voice 20 pots
no sip-register
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide