Integrating 3CX with Cisco Call Manager Express and Unity

Status
Not open for further replies.

mlump

Joined
Feb 24, 2012
Messages
113
Reaction score
1
I have recently been asked to integrate 3CX with our existing Cisco Cisco Call Manager Express and Unity Express system.
Cisco CME IP address is: 10.10.10.1
Cisco Unity IP address is: 10.1.10.1
3CX Server IP address is: 10.10.10.254

I have a VoIP Provider setup on 3CX that does successfully connect with the Cisco Call manager (CME) and i do have calls flowing back and forth. However when you call a Cisco ext from a 3CX ext and the Cisco ext does not answer the Cisco CME then diverts the call to Unity by Sending a SIP "Moved Temporarily" message that has a contact field of [email protected] which is the ext and IP of Unity. At this point 3CX terminates the call with No Known route to [email protected]. See Logs below:

14:34:38.096 [CM503020]: Normal call termination. Reason: Terminated
14:34:38.095 [CM503016]: Call(36): Attempt to reach <sip:[email protected]> failed. Reason: Redirected
14:34:38.056 [CM503003]: Call(36): Call to sip:[email protected]:5060 has failed; Cause: 302 Moved Temporarily; from IP:10.10.10.1:5060
14:34:38.041 [CM503014]: Call(36): No known route to target: <sip:[email protected]>
14:34:38.038 [CM503006]: Call(36): Diverted to: <sip:[email protected]>
14:34:36.562 [CM505003]: Provider:[Cisco] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cisco-SIPGateway/IOS-12.x] PBX contact: [sip:[email protected]:5060]
14:34:36.562 [CM503002]: Call(36): Alerting sip:[email protected]:5060
14:34:36.352 [CM503025]: Call(36): Calling VoIPline:2042@(Ln.10000@Cisco)@[Dev:sip:[email protected]:5060]
14:34:36.293 [MS210002] C:36.2:Offer provided. Connection(transcoding mode): 10.10.10.254:7160(7161)
14:34:36.239 [CM503004]: Call(36): Route 1: VoIPline:2042@(Ln.10000@Cisco)@[Dev:sip:[email protected]:5060]
14:34:36.232 [CM503010]: Making route(s) to <sip:[email protected]>
14:34:36.230 [MS210000] C:36.1:Offer received. RTP connection: 10.10.10.80:11788(11789)
14:34:36.222 Remote SDP is set for legC:36.1
14:34:36.221 [CM505001]: Ext.2500: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Yealink SIP-T32G 32.0.0.106] PBX contact: [sip:[email protected]:5060]
14:34:36.140 [CM503001]: Call(36): Incoming call from Ext.2500 to <sip:[email protected]>
14:34:36.082 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 10.10.10.80:5062;branch=z9hG4bK1605795914
Max-Forwards: 70
Contact: <sip:[email protected]:5062>
To: <sip:[email protected]>
From: "test this"<sip:[email protected]>;tag=591110465
Call-ID: [email protected]
CSeq: 2 INVITE
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Proxy-Authorization: Digest username="2500",realm="3CXPhoneSystem",nonce="414d535c05fbe33b91:1b895517311c9bc0031342dd64489a14",uri="sip:[email protected]",response="449ab7712f754acfcee77c299aea0844",algorithm=MD5
Supported: replaces
User-Agent: Yealink SIP-T32G 32.0.0.106
Allow-Events: talk, hold, conference, refer, check-sync
Content-Length: 0

I can Successfully dial the unity ext by dialing 6000 from a 3CX phone. I have also tried creating a second VoIP provider that connect directly to the unity IP and can dial ext. 6000 using that also. I have also turned on direct sip calling and can call [email protected] directly with no issues. However every-time 3CX receives the SIP "Moved Temporarily" message i get the above results. This is a bit of a show stopper and i need to get this fixed. Any advice would help greatly.

Thank you,
Mike Lump
ComResource a Premier 3CX Partner
 
Re: Integrating 3CX with Cisco Call Manager Express and Unit

I found the solution to this a while back if anyone is interested. Since 3CX does not support Moved Temporarily responses from a SIP Trunk I had to disable the 302 Moved Temporarily from being sent on the Cisco end. What this forces the Cisco CME to do is Hairpin the call and corrects the problem.
 
Status
Not open for further replies.