Cisco Unified Application Environment Developer Forums

« Back to Developers

RE: Call failed to SIP device

Combination View Flat View Tree View
Threads [ Previous | Next ]
Call failed to SIP device
Answer
5/13/10 12:23 AM
Hi,
 
I have a call script that attempts a MakeCall to a 7961 phone defined in my CUCM.  I have ensured that the following pre-requisites are set up and configured properly, and both CUAE & CUCM are on the same subnet and can communicate with each other.
 
on CUAE:
 
1. Connection set up to CUCM with call call control selected.
2. SIP group defined with trunk interface set to CUCM IP addr.
3. Media engine set up and connected.
4. Call script application set up to route call to SIP route group.
 
on CUCM:
 
1. Two devices set up for each 7961 phone, and line number.
2. Set up calling search space and associated with each phone.
3. SIP Trunk set up and set to same calling search space.
4. SIP Security profile set up and associated with SIP Trunk.
5. SIP Profile set up and associated with SIP Trunk.
 
My script attempts to dial the 1st phone, then perform a blind transfer to the second.  Yet when the script dials the first phone, I get a MakeCall failed returned along with the following log snippet:
 
2010:05:10::14:37:43(03): Warning: C2C-4 Application: C2C Initiating Host: 161.44.114.213 To:1001  From:1000 useallowed=False
2010:05:10::14:37:43(10): Info: SIP Added Sip callId 1000004 stackCallId
2010:05:10::14:39:15(89): Warning: TM  Acting on timeout condition (1000004emoticonutboundCall_WaitTxRx:1)
0,cpu=1.136378%,mem=171417KB:

2010:05:10::14:39:15(90): Info: SIP HandleTerminateCall
2010:05:10::14:39:15(90): Warning: TM  Outbound call attempt to '1000' failed. Reason: Normal
 
Are there any steps missing that would cause the outbound call failure as seen here?  What else could cause this error?
 
Thanks,
 
Bill
Flag

RE: Call failed to SIP device
Answer
5/14/10 4:34 PM as a reply to William Honneus.
Hi Bill,
 
In the CUAEAdmin, go to Plugins->List Plugins. Click on the SIP Provider. Could you please check if the "DefaultOutboundFromNumber" is specified? If not specified add any dummy number there. See if this helps you to get the makeCall working.
 
For the BlindTranfer to work, make sure on the CUCM side the Re-Routing Calling Search Space is properly set. Transfer will fail if this not set properly.
 
Thanks
Nabhonil
Flag

RE: Call failed to SIP device
Answer
5/27/10 6:49 PM as a reply to Nabhonil Sinha.
Hi Nabhonil,
 
I was able to get the MakeCall working with some changes to my SIP trunk configuration.  I am using a private network with CUAE/CUCM IP addresses in the 192.168.x.x space, and there seemed to be an issue in rerouting the SIP traffic using the external IP of the CUAE in the SIP trunk and Media Engine configurations.  So now I have all configured using just the internal IP addresses.
 
As for the Blind Transfer, this is still not working.  I have a verbose trace from CUAE which seems to indicate that the CUAE is tearing down the call before CUCM has a chance to send the reply back for the transfer request sent by CUAE.
 
Here is the trace:
 
2010:05:25::16:15:40(39): Warning: C2C-4 Application: C2C Initiating Host: 10.86.240.111 To:1001  From:1000 useallowed=False
2010:05:25::16:15:40(40): Info: SIP Added Sip callId 1000004 stackCallId
2010:05:25::16:15:40(40): Verbose: SIP Sent MakeCall. stackCallId:1000004, to:1000, dn:192.168.110.5, deviceType:SipTrunk, from:, rxIP:, rxPort:0
2010:05:25::16:15:40(42): Verbose: SIP Got 148(MakeCallAck) message.
2010:05:25::16:15:40(42): Verbose: SIP Field: 0(ResultCode) = 0
2010:05:25::16:15:40(42): Verbose: SIP Field: 2(CallId) = 1000004
2010:05:25::16:15:40(42): Verbose: SIP Field: 6(StackCallId) = 9d2695025a1d6605@Q0lTQ08tV01aU0NCSTJI;d60b4a73
2010:05:25::16:15:40(42): Verbose: SIP Received MakeCallACK for 1000004
2010:05:25::16:15:42(37): Verbose: SIP Got 143(MediaEstablished) message.
2010:05:25::16:15:42(37): Verbose: SIP Field: 2(CallId) = 1000004
2010:05:25::16:15:42(37): Verbose: SIP Field: 6(StackCallId) = 9d2695025a1d6605@Q0lTQ08tV01aU0NCSTJI;d60b4a73;3ba8b1e7-a983-43ef-804d-c1543a1e3b8d-32527024
2010:05:25::16:15:42(37): Verbose: SIP Field: 7(TxIp) = 192.168.110.60
2010:05:25::16:15:42(37): Verbose: SIP Field: 8(TxPort) = 4000
2010:05:25::16:15:42(37): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(37): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(37): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(37): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(37): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(37): Verbose: SIP Got 150(Answered) message.
2010:05:25::16:15:42(39): Verbose: SIP Field: 2(CallId) = 1000004
2010:05:25::16:15:42(39): Verbose: SIP Field: 6(StackCallId) = 9d2695025a1d6605@Q0lTQ08tV01aU0NCSTJI;d60b4a73;3ba8b1e7-a983-43ef-804d-c1543a1e3b8d-32527024
2010:05:25::16:15:42(39): Verbose: SIP Field: 7(TxIp) = 192.168.110.60
2010:05:25::16:15:42(39): Verbose: MCP connect message sent successfully
2010:05:25::16:15:42(39): Verbose: SIP Field: 8(TxPort) = 4000
2010:05:25::16:15:42(39): Verbose: SIP Field: 16(DisplayName) = Click To Call App
2010:05:25::16:15:42(39): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(39): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(39): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(39): Verbose: MEP Sending success response (1:8414)
2010:05:25::16:15:42(39): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(39): Verbose: SIP Field: 18(MediaCaps) = 18 20
2010:05:25::16:15:42(39): Verbose: SIP Field: 20(From) = 89999999
2010:05:25::16:15:42(39): Verbose: SIP Field: 21(To) = 1000
2010:05:25::16:15:42(39): Verbose: SIP Field: 30(OriginalTo) =
2010:05:25::16:15:42(39): Verbose: SIP Field: 38(MediaOption) = 1
2010:05:25::16:15:42(39): Verbose: SIP Field: 42(DirectoryNumber) = 1000@192.168.110.5
2010:05:25::16:15:42(39): Verbose: SIP HandleSetMedia-New media info: callId=1000004, rxIp=192.168.110.125, rxPort=20486, rxCodec=Unspecified, txCodec=G711u, framesize=20
2010:05:25::16:15:42(39): Verbose: SIP HandleSetMedia-Old media info: callId=1000004, rxIp=, rxPort=0, rxCodec=Unspecified, framesize=0, state=Active
2010:05:25::16:15:42(39): Verbose: SIP Sent SetMedia. stackCallId:1000004, rxIP:192.168.110.125, rxPort:20486
2010:05:25::16:15:42(40): Verbose: MCP connect message sent successfully
2010:05:25::16:15:42(43): Verbose: MEP Sending success response (1:8415)
2010:05:25::16:15:42(46): Verbose: SIP Sent BlindTransfer. stackCallId:9d2695025a1d6605@Q0lTQ08tV01aU0NCSTJI;d60b4a73;3ba8b1e7-a983-43ef-804d-c1543a1e3b8d-32527024, to:1001
2010:05:25::16:15:42(48): Verbose: MCP disconnect message sent successfully
2010:05:25::16:15:42(50): Verbose: MEP Sending success response (1:8416)
2010:05:25::16:15:54(37): Verbose: SIP Got 151(ReInvite) message.
2010:05:25::16:15:54(37): Verbose: SIP Field: 2(CallId) = 1000004
2010:05:25::16:15:54(37): Verbose: SIP Field: 6(StackCallId) = 9d2695025a1d6605@Q0lTQ08tV01aU0NCSTJI;d60b4a73;3ba8b1e7-a983-43ef-804d-c1543a1e3b8d-32527024
2010:05:25::16:15:54(37): Verbose: SIP Field: 7(TxIp) = 192.168.110.60
2010:05:25::16:15:54(37): Verbose: SIP Field: 8(TxPort) = 26254
2010:05:25::16:15:54(37): Verbose: SIP Field: 16(DisplayName) =
2010:05:25::16:15:54(37): Verbose: SIP Field: 18(MediaCaps) = 101 0
2010:05:25::16:15:54(37): Verbose: SIP Field: 18(MediaCaps) = 101 0
2010:05:25::16:15:54(37): Verbose: SIP Field: 20(From) = 1000
2010:05:25::16:15:54(37): Verbose: SIP Field: 21(To) = 89999999
2010:05:25::16:15:54(37): Verbose: SIP Field: 30(OriginalTo) =
2010:05:25::16:15:54(37): Verbose: SIP Field: 38(MediaOption) = 0
2010:05:25::16:15:54(37): Verbose: SIP Field: 42(DirectoryNumber) = 89999999@192.168.110.5
2010:05:25::16:15:54(37): Warning: SIP Received ReInvite message for non-existent call: 1000004
2010:05:25::16:15:54(37): Verbose: SIP Sent Hangup. stackCallId:9d2695025a1d6605@Q0lTQ08tV01aU0NCSTJI;d60b4a73;3ba8b1e7-a983-43ef-804d-c1543a1e3b8d-32527024
2010:05:25::16:15:54(37): Verbose: SIP Got 203(Hangup) message.
2010:05:25::16:15:54(37): Verbose: SIP Field: 2(CallId) = 1000004
2010:05:25::16:15:54(37): Verbose: SIP Field: 6(StackCallId) = 9d2695025a1d6605@Q0lTQ08tV01aU0NCSTJI;d60b4a73;3ba8b1e7-a983-43ef-804d-c1543a1e3b8d-32527024
2010:05:25::16:15:54(37): Verbose: SIP Field: 17(CallEndReason) = Application ended the call.

What I don't understand is why the Reinvite is attempting to make a call from device 1000 (1st 7961 defined in CSS) to 8999999 (CUAE initiating number), when it should be making the call to 1001 (2nd 7961).
 
CUCM traces can be sent upon request.  This is using CUAE 2.5.1.1 SR2 and CUCM 7.1.3.
 
Thanks,
 
Bill
Flag