Endpoints Registration rejected

[binu.john]

Hi all,

We have a VCS with X6.1 with Profile and EX Series registered, when i tried to regsiter a new one iam getting registration failed and in the VCS logs i could see status rejected for both H323 and SIP. Reason: "Not permitted by Policy".

The existing endpoints which were registered before are still registered with H323 but not SIP.

Iam attaching the error log snap.

There is no configuration made on Registration Policy.

H323 and SIP are on and shows Active.

May 15 12:28:01    tvcs: Event="Registration Requested" Service="SIP" Src-ip="200.101.2.32" Src-port="5061" Protocol="TLS" AOR="5559@ec.com" Contact="sip:5559@200.101.2.32:5061;transport\=tls" Duration="60" Level="1" UTCTime="2012-05-15 08:28:01,285"

May 15 12:28:01    tvcs: Event="Registration Refresh Rejected" Reason="AOR is not permitted by registration policy" Service="SIP" Src-ip="200.101.2.32" Src-port="5061" Protocol="TLS" AOR="5559@ec.com" Contact="sip:5559@200.101.2.32:5061;transport\=tls" Duration="60" Level="1" UTCTime="2012-05-15 08:28:01,285"

May 15 12:27:58    tvcs: Event="Registration Rejected" Reason="Not permitted by policy" Service="SIP" Src-ip="200.101.70.11" Src-port="5061" Protocol="TLS" AOR="5590@ec.com" Contact="sip:5590@200.101.70.11:5061;transport\=tls" Duration="60" Level="1" UTCTime="2012-05-15 08:27:58,897"

May 15 12:27:58    tvcs: Event="Registration Requested" Service="SIP" Src-ip="200.101.70.11" Src-port="5061" Protocol="TLS" AOR="5590@ec.com" Contact="sip:5590@200.101.70.11:5061;transport\=tls" Duration="60" Level="1" UTCTime="2012-05-15 08:27:58,897"

May 15 12:27:58    tvcs: Event="Registration Refresh Rejected" Reason="AOR is not permitted by registration policy" Service="SIP" Src-ip="200.101.70.11" Src-port="5061" Protocol="TLS" AOR="5590@ec.com" Contact="sip:5590@200.101.70.11:5061;transport\=tls" Duration="60" Level="1" UTCTime="2012-05-15 08:27:58,897

Anyone came across this?

[awinter2]

Hi,

have you verified that this AOR (5559@ec.com) is not already registered in SIP?

Does 'ec.com' exist as a SIP domain on this VCS?

Can you verify that the Default Subzone (Or any other relevant subzone) is not configured with a registration policy of ''Deny'?

Is there any CPL running on this VCS?

- Andreas

[binu.john]

Hi Andreas,

All our endpoints are registered with SIP and H323.

1)Yes 5559@ec.com are registered as SIP.

2)ec.com is configured on VCS as SIP Domain.

3)Default subzone config is set as 'deafult'.

Even when i tried to regsiter a new endpoint today, it was rejecting both h323 and SIP. with reason code= not permitted by policy".

Thanks

John

[awinter2 · Accepted solution]

So if 5559@ec.com is already registered on SIP, is the registration request for 5559@ec.com from

200.101.2.32 originating from a different endpoint that's currently holding this registration?

Is there any CPL/Admin policy active on this VCS?

You initially mentioned that no registration policy was in use, but can you please verify that VCS Configuration > Registration > Configuration > Restriction Policy is set to 'None'?

- Andreas

[binu.john]

   1)    

No, there is only 1 endpoint in the network with 5559 ID. Looks like on 5559 SIP was unregistered, and its trying to register back.

2) CPL-No Admin Policy is set.

3) Restrictions- Its default value, no changes made. I dont have access to the system now, i will check this and get back to you.

Can i have your email.?

Thanks

[awinter2]

John,

let's keep the discussion on the forum so that others can benefit from the findings as well.

- Andreas

[binu.john]

Thanks Andreas,

Got it!, it was on the vcs-resctriction policy config.

Cheers

John

[Jens Didriksen]

I've had a similar issue in the past where SIP registrations were rejected, turned out it was caused by h.323 id and SIP address being identical, i.e.with both h323 id and SIP using b1102, the SIP registration would be rejected.

Changing h323 id slightly to b1-102 fixed it. Might not be the cause of your issue, but I thought I'd mention it just in case.

/jens