Cisco Jabber Calls to H323 Endpoint in VCS not working

Nishad Ismail · ‎04-25-2017

Hi Team,

Cisco Jabber Calls to H323 Endpoint in VCS,But calls is not working

Error in VCS "480 Temporarily Not Available"

---------------------------------------------------------------

2017-04-25T11:06:16+03:00 tvcs: Event="Call Rejected" Service="SIP" Src-ip="10.16.9.12" Src-port="5060" Src-alias-type="SIP" Src-alias="sip:1114@10.16.9.12" Dst-alias-type="SIP" Dst-alias="sip:4001@10.16.11.10:5060" Call-serial-number="0eab99e8-298e-11e7-b995-0010f32d00f8" Tag="0eab9b96-298e-11e7-b976-0010f32d00f8" Detail="Temporarily Not Available" Protocol="TCP" Response-code="480" Level="1" UTCTime="2017-04-25 08:06:16,694"
2017-04-25T11:06:16+03:00 tvcs: Event="Search Completed" Reason="Temporarily Not Available" Service="SIP" Src-alias-type="SIP" Src-alias="1114@10.16.9.12" Dst-alias-type="SIP" Dst-alias="sip:4001@10.16.11.10:5060" Call-serial-number="0eab99e8-298e-11e7-b995-0010f32d00f8" Tag="0eab9b96-298e-11e7-b976-0010f32d00f8" Detail="found:false, searchtype:INVITE" Level="1" UTCTime="2017-04-25 08:06:16,694"
2017-04-25T11:06:16+03:00 tvcs: Event="Call Attempted" Service="SIP" Src-ip="10.16.9.12" Src-port="5060" Src-alias-type="SIP" Src-alias="sip:1114@10.16.9.12" Dst-alias-type="SIP" Dst-alias="sip:4001@10.16.11.10:5060" Call-serial-number="0eab99e8-298e-11e7-b995-0010f32d00f8" Tag="0eab9b96-298e-11e7-b976-0010f32d00f8" Protocol="TCP" Auth="NO" Level="1" UTCTime="2017-04-25 08:06:16,633"
2017-04-25T11:06:16+03:00 tvcs: Event="Search Attempted" Service="SIP" Src-alias-type="SIP" Src-alias="1114@10.16.9.12" Dst-alias-type="SIP" Dst-alias="sip:4001@10.16.11.10:5060" Call-serial-number="0eab99e8-298e-11e7-b995-0010f32d00f8" Tag="0eab9b96-298e-11e7-b976-0010f32d00f8" Detail="searchtype:INVITE" Level="1" UTCTime="2017-04-25 08:06:16,633"

------------------------------------------------------------

Endpoint Cisco Jabber:SIP (Registered in CUCM)

TP Endpoint Cisco Profile 65 :H323 (Registered in VCS)

CUCM 9.x (SIP trunk to VCS)

VCS 7.2(Neighbour Zone to CUCM)

Alok Jaiswal · ‎04-25-2017

This are all info level logs, plus its post the search completed. It is not possible to figure out the exact problem.

But try to see if your H.323 endpoint registered as E.164 or H.3233 ID (with domain for e.g.) it matches to the number/URI coming in. Though in that case i expect VCS to generate a different error.

Can you attach the diagnostic logs from VCS. Plus the VCS vresion x7.2 is very old. You are living in past, get your VCS upgraded to enjoy new features and better interoperability.

Regards,

Alok

Nishad Ismail · ‎05-04-2017

Dear Alok,

Am getting the same issue while dialing from TX9200(CUCM) to Profile 65(VCS)

Attached the diagnostic logs of VCS

Regards,

Nishad KI

Alok Jaiswal · ‎05-05-2017

I think you are running a very old version of VCS (7.x), that's why diagnostic logs is in info. You need to set to debug while collecting the logs.

Though i think i might have potentially find the issue. Is it the below call are you referring to ??

2017-05-04T19:36:24+03:00 heruhitvcsc01 tvcs: Event="Search Attempted" Service="SIP" Src-alias-type="SIP" Src-alias="4000@10.16.9.12" Dst-alias-type="SIP" Dst-alias="sip:4001@10.16.11.10:5060" Call-serial-number="d00eeed6-30e7-11e7-9fea-0010f32d00f8" Tag="d00ef084-30e7-11e7-8924-0010f32d00f8" Detail="searchtype:INVITE" Level="1" UTCTime="2017-05-04 16:36:24,433"

If that's the case then i think the issue is your destination alias is coming as "sip:4001@10.16.11.10:5060" and you need to create a transform to strip off the port also you need to check how endpoinnt 4001 is registered as ? with an E.164 (4001) or H.323 ID (4001@domain) for e.g.

And based on that while doing the transform change the resultant destination address.

regards,

Alok

Acevirgil de Ocampo · ‎04-27-2017

Hi,

First is we need to know how the CUCM and VCS are deployed in the network. Is there any firewall in between them? How about the status of the SIP trunk, is it active?

Share also the search history of that call from your VCS.

regards,

Acevirgil

Ammar Saood · ‎05-05-2017

1. can H323 endpoint call Jabber client ? (if YES)

2. is interworking enable in VCS.? (if YEX)

3. is there any CPL policy active or enabled ?

4. is there a local search rule with protocol any ??

5. are you dialing with domain (SIP URI) or just the IP Address or prolfile65 ?

you are dialing from 1114 to 4001.

kindly add the transform to convert VCS IP to domain (10.16.11.10 to @vcsdomain.com)

because the endpoint in VCS is registered as 4001@vcsdomain.com not 4001@10.16.11.10.

or you can create a search rule.

to replace (.*)@10.16.11.10 to (.*)@vcsdomain.com and point it to local Zone.

HTH

AMMAR

please rate and mark answered if helpful.