A few weeks before, it's working when the Movi(reside in VCS-C X7.2) calling Cisco Jabber for Windows(reside in CUCM 9.0), and I did the integration configuration according to the below link:
http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Cisco_Unified_Communications_Manager_Deployment_Guide_CUCM_8_9_and_X7-2.pdf
but recently, I found the Movi couldn't reach the Cisco Jabber for windows when dialing the 4 digit extension, I did an re-check for both configuration on VCS-C and CUCM, it looks fine.
So I did an debug in VCS-C, and found below feedback which might be the core issue, but anyone could can point me an insight on this? But what's the problem?
2013-02-02T14:21:45+08:00 vcsc tvcs: UTCTime="2013-02-02 06:21:45,545" Module="network.sip" Level="INFO": Src-ip="cucm's IP" Src-port="5060" Detail="Receive Response Code=503, Method=INVITE, To=sip:1001@xxx.com, Call-ID=765ff5ae569b7e87@172.17.0.14"
2013-02-02T14:21:45+08:00 vcsc tvcs: UTCTime="2013-02-02 06:21:45,546" Module="network.sip" Level="DEBUG": Src-ip="cucm's IP" Src-port="5060"
SIPMSG:
|SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP cucm's IP:5060;egress-zone=CUCMNeighbor;branch=z9hG4bK45fb9fc08a40a84d401ea90f3b71e053324163.aec65039ec6c7ba030da8842cd0403d3;proxy-call-id=d15db2d6-6d00-11e2-9a66-000c29f34519;rport,SIP/2.0/TLS 172.17.0.14:51949;branch=z9hG4bK8f6932314ce68712d4645221ac36e661.1;received=Movi's IP;rport=51949;ingress-zone=DefaultSubZone
Call-ID: 765ff5ae569b7e87@172.17.0.14
CSeq: 100 INVITE
From: "AAA" <sip:aaa@xxx.com>;tag=3ed658e203e2850a
To: <sip:1001@xxx.com>;tag=105854~d841f777-9ff4-458e-bf52-e8ed52c35ecc-28265121
Date: Sat, 02 Feb 2013 06:21:45 GMT
Allow-Events: presence
Reason: Q.850 ;cause=41
Content-Length: 0
|
