Solved: MX200 (TC6.2) can't register with SIP TLS to VCS Control

AbdullahDB · ‎08-26-2013

Dear all,

I just received a brand new MX200 in our labs.

We're evaluating at the moment the global upgrade to TC6.2 sw version.

The MX200 has been delivered with TC6.1.1.7. Registering at the VCS Control with SIP TLS works without any problems at all.

VCS-C eventlog:

Aug 26 14:16:47 tvcs: Event="Registration Accepted" Service="SIP" Src-ip="172.18.93.88" Src-port="5061" Protocol="TLS" AOR="MX200@DOMAIN.com" Contact="sip:MX200@172.18.93.88:5061;transport\=tls" Duration="60" Level="1" UTCTime="2013-08-26 14:16:47,833"

Aug 26 14:16:47 tvcs: Event="Registration Requested" Service="SIP" Src-ip="172.18.93.88" Src-port="5061" Protocol="TLS" AOR="MX200@DOMAIN.com" Contact="sip:MX200@172.18.93.88:5061;transport\=tls" Duration="60" Level="1" UTCTime="2013-08-26 14:16:47,831"

After upgrading to TC6.2 the registration fails.

Aug 26 14:36:26 tvcs: Event="Registration Rejected" Reason="Received from unauthenticated source" Service="SIP" Src-ip="172.18.93.88" Src-port="36545" Protocol="TLS" AOR="sip:DOMAIN.com" Contact="<sip:MX200@172.18.93.88:5061;transport\=tls>;+sip.instance\="<urn:uuid:5b8eacf1-43e0-5f37-b5c6-74e28c5ca854>"" Duration="3600" Level="1" UTCTime="2013-08-26 14:36:26,481"

Aug 26 14:36:26 tvcs: Event="Registration Requested" Service="SIP" Src-ip="172.18.93.88" Src-port="36545" Protocol="TLS" AOR="sip:DOMAIN.com" Contact="<sip:MX200@172.18.93.88:5061;transport\=tls>;+sip.instance\="<urn:uuid:5b8eacf1-43e0-5f37-b5c6-74e28c5ca854>"" Duration="3600" Level="1" UTCTime="2013-08-26 14:36:26,481"

As far as I can see there is something not really working with the protocoll in connection with the SIP URI (AOR). I'm missing the prefix "MX200@DOMAIN.com"

All other systems (profile, ex, sx) are working fine with TC6.2.

Does anyone has an idea?

Alok Jaiswal · ‎08-26-2013

Hi Abdullah,

since the registration "AOR" is only says AOR="sip:DOMAIN.com"

i belive you must be having some sort of search rule on the VCS matching to the sip domain and pointing towards traversal or a neighbour zone and there the policy setting must be "check credentials".

and since there is no username/password available the registration attempts fails with the message "received from un-authenticated source".

did you recently created any transforms on the VCS? also recheck your endpoint configuration.

you can create a rule to send this registration message through local zone which in turn will go through to subzone for registration. please note the subzone should be set to "treat as authenticated" if you are not using the authentication.

Rgds

Alok

View solution in original post

Alok Jaiswal · ‎08-26-2013

Hi Abdullah,

since the registration "AOR" is only says AOR="sip:DOMAIN.com"

i belive you must be having some sort of search rule on the VCS matching to the sip domain and pointing towards traversal or a neighbour zone and there the policy setting must be "check credentials".

and since there is no username/password available the registration attempts fails with the message "received from un-authenticated source".

did you recently created any transforms on the VCS? also recheck your endpoint configuration.

you can create a rule to send this registration message through local zone which in turn will go through to subzone for registration. please note the subzone should be set to "treat as authenticated" if you are not using the authentication.

Rgds

Alok

AbdullahDB · ‎08-26-2013

Hello Alok,

thanks for your advice.

For some reason, after the upgrade, the password of the authentication wasn't used by the codec - the field was completly blank.

After setting the password again the registration worked.

IMHO before upgrading to TC6.2 it's necessary to configure the system in TC6.1.1.7 and then do the upgrade.

When I was upgrading without a configuration and do the first configuration with TC6.2 it didn't save the password.

Did anyone else had these symptoms?

KR