11-04-2022 10:47 AM
I have a SIP phone registered to CME on 12.4 Ive tried everything to keep the phone from trying to register to the ITSP
I have tried: voice register dn, no-reg. Still trying to register to ITSP.
I tried: voice register global, max-dn 15 no-reg both resulting in an invalid command.
Also: telephony-service, no auto-reg-ephone but that didnt work either.
r#show sip-ua register status
Line peer expires(sec) registered
================================ ========== ============ ==========
1003 40001 46 no
247121 -1 2196 yes
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK87791E8E;received=xxx.xxx.xxx.xxx;rport=21834
From: <sip:1003@xxx.xxx.xxx.xxx>;tag=1ED10750-195F
To: <sip:1003@xxx.xxx.xxx.xxx>;tag=as6a7dfea5
Call-ID: DBD31A66-5B3511ED-A0DFA617-75C059C4
CSeq: 484 REGISTER
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="seattle.voip.ms", nonce="5706cd39"
Content-Length: 0
11-04-2022 11:57 PM - edited 11-06-2022 01:21 AM
If you’re using registration for the SIP trunk from your ITSP you’d need to use tenant configuration for this to define the registrar for the trunk. This is because the registrar defined under sip-ua is global and needs to be set to the CME for the SIP phones to register with CME. If you need help with what to change please share your running configuration so that we can suggest the appropriate changes.
11-05-2022 12:11 AM - edited 11-08-2022 02:21 AM
similar issue with me, and i'm unable to resolve it
11-06-2022 01:17 AM
If you share your running configuration we can advise you on what you’ll need to do.
11-07-2022 06:15 AM
Hi,
If your SIP trunk registration is using an outbound proxy, then you can also try the below:
voice register global
no outbound-proxy
Make sure to do a "create profile" after this.
HTH
Rajan
Please mark all useful posts as helpful and solutions as accepted wherever applicable
04-10-2024 10:49 PM
I wonder if you ever resolved this? I agree, the no-reg commands seem to have no effect whatsoever on certain dns.
I have also tried using a tenant which made no effect, it repeatedly tries to register certain dns to that tenant.
04-11-2024 03:11 AM
If you share your running configuration we can advise you on what you’ll need to modify.
04-11-2024 03:16 AM
It was fixed by a reload, and by re-applying the no-reg both commands to some of the ephone-dns. I'm going to have to conclude it was a bug (one of many) in CME.
Under show telephony-service dial-peer, some dial-peers were missing no e164 registration despite having no-reg both. This was fixed for some of them by re-entering the same number command under ephone-dn, but there were a couple of stubborn entries which would not disappear from sh sip-ua register status until it was reloaded.
My main concern is whether those phantom registrations will come back. I checked and the no-reg both change does appear to have persisted after a reload.
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