cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1424
Views
5
Helpful
4
Replies

PHONE IS TRYING TO REGISTER WITH ITSP AS AGAINST CME

Jesutofunmi O
Level 1
Level 1

Hello Guys, 

 

I got a SIP trunk from an ITSP but have been unable to register it. The problem is that the ITSP's SBC is rejecting my sip-ua registration request (from CME) because the requests coming from my CME are too many.  MY Cisco 7945 PHONES ARE ALSO SENDING REGISTRATION REQUESTS TO THE ITSP.  PLEASE HOW DO I STOP THIS? HELP!!!



May 30 17:08:59.893: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:cme.telecoms.com:5060 SIP/2.0
Via: SIP/2.0/UDP 41.xx.xx.xx:5060;branch=z9hG4bK5441614
From: <sip:1022@cme.telecoms.com>;tag=B7C5104-F1C
To: <sip:1022@cme.telecoms.com>
Date: Thu, 30 May 2019 17:08:59 GMT
Call-ID: 3DF091F9-823111E9-B65BE35C-F9412332
User-Agent: Cisco-SIPGateway/IOS-15.3.3.M5
Max-Forwards: 70
Timestamp: 1559236139
CSeq: 2 REGISTER
Contact: <sip:1022@41.xx.xx.xx:5060>
Expires: 3600
Supported: path
Content-Length: 0


May 30 17:08:59.901: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:cme.telecoms.com:5060 SIP/2.0
Via: SIP/2.0/UDP 41.xx.xx.xx:5060;branch=z9hG4bK5482262
From: <sip:1026@cme.telecoms.com>;tag=B7C5110-55E
To: <sip:1026@cme.telecoms.com>
Date: Thu, 30 May 2019 17:08:59 GMT
Call-ID: 3DF12EBA-823111E9-B65FE35C-F9412332
User-Agent: Cisco-SIPGateway/IOS-15.3.3.M5
Max-Forwards: 70
Timestamp: 1559236139
CSeq: 2 REGISTER
Contact: <sip:1026@41.xx.xx.xx:5060>
Expires: 3600
Supported: path
Content-Length: 0


May 30 17:09:00.041: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:cme.telecoms.com:5060 SIP/2.0
Via: SIP/2.0/UDP 41.xx.xx.xx:5060;branch=z9hG4bK552E16
From: <sip:1036@cme.telecoms.com>;tag=B7C5194-103
To: <sip:1036@cme.telecoms.com>
Date: Thu, 30 May 2019 17:09:00 GMT
Call-ID: 3DF12EBA-823111E9-B669E35C-F9412332
User-Agent: Cisco-SIPGateway/IOS-15.3.3.M5
Max-Forwards: 70
Timestamp: 1559236140
CSeq: 2 REGISTER
Contact: <sip:1036@41.xx.xx.xx:5060>
Expires: 3600
Supported: path
Content-Length: 0


May 30 17:09:00.053: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:cme.telecoms.com:5060 SIP/2.0
Via: SIP/2.0/UDP 41.xx.xx.xx:5060;branch=z9hG4bK554D8C
From: <sip:1038@cme.telecoms.com>;tag=B7C519C-1A60
To: <sip:1038@cme.telecoms.com>
Date: Thu, 30 May 2019 17:09:00 GMT
Call-ID: 3DF12EBA-823111E9-B66BE35C-F9412332
User-Agent: Cisco-SIPGateway/IOS-15.3.3.M5
Max-Forwards: 70
Timestamp: 1559236140
CSeq: 2 REGISTER
Contact: <sip:1038@41.xx.xx.xx:5060>
Expires: 3600
Supported: path
Content-Length: 0

1 Accepted Solution

Accepted Solutions

So people who come after can find a solution. I already found a fix to this. 

This solved it for me;

Go to ephone-dn and issue the "no-reg" command after "number xxxx no-reg". Example below;

 

ephone-dn 1 dual-line
number 1001 no-reg 
label John Smith
description John Smith

 

I hope someone else finds this helpful

 

 

View solution in original post

4 Replies 4

Is your CME a registrar server? What IPs does your phones have for TFTP servers?

 

Rolando A. Valenzuela

Hello Rolando, 

1. My CME is the registrar server (at least all phones can call each other-intercom and dial-peers)

2. The TFTP server address is the address of the CME 172.16.xx.xx

So people who come after can find a solution. I already found a fix to this. 

This solved it for me;

Go to ephone-dn and issue the "no-reg" command after "number xxxx no-reg". Example below;

 

ephone-dn 1 dual-line
number 1001 no-reg 
label John Smith
description John Smith

 

I hope someone else finds this helpful

 

 

If someone wants to do the same for SIP phones:

There is no no-reg in voice register global, you only configure it in the dn:
voice register dn 1
  number 1001
  no-reg


If that doesn't work...

In my case, the router still sent the registration of the phone to the provider after that. I unplugged the phone, no change. I removed the phone (pool and dn) config, no change. I removed the sip-ua for the connection to the provider but once I moved it back, the router did the same thing. In the end, only a reload could fix the problem.