02-11-2013 02:01 AM - edited 03-16-2019 03:38 PM
Hi Guys,
I have problem at one of our customer side. When an operator received a call, and try to do a transfer (consult transfer) to a colleague, the colleague's phone ring one time and the call failed. The operator have to take back the call and give the full external number of the colleague to the caller.
After a reboot of the phone (unplugged/plugged) the transfer work fine !
I tried to find the cause in the CUCM traces but I need help.
Saw that Refer messages:
14:49:26.294 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 22.212.126.35 on port 50108 index 227
[21667403,NET]
REFER sip:15026@22.212.126.35:50108 SIP/2.0
Via: SIP/2.0/TCP 22.214.10.18:5060;branch=z9hG4bKf63095b1b37b1
From: <sip:15026@22.214.10.18>;tag=435147058
To: <sip:15026@22.212.126.35>
Call-ID: 2e587c80-1131b0e6-4ef59-120ad616@22.214.10.18
CSeq: 101 REFER
Max-Forwards: 70
Contact: <sip:15026@22.214.10.18:5060;transport=tcp>
User-Agent: Cisco-CUCM8.6
Require: norefersub
Expires: 0
Refer-To: cid:1234567890@22.214.10.18
Content-Id: <1234567890@22.214.10.18>
Content-Type: application/x-cisco-remotecc-request+xml
Referred-By: <sip:15026@22.214.10.18>
Content-Length: 341
<x-cisco-remotecc-request>
<answercallreq>
<dialogid>
<callid>2a2c5f00-1131b0df-4ef4b-120ad616@22.214.10.18</callid>
<localtag>6511241~ada938a2-d3e6-4928-be65-07fc5a6e0f23-49485024</localtag>
<remotetag>3cce73acbe00bd3fda57ded7-91adfcf9</remotetag>
</dialogid>
</answercallreq>
</x-cisco-remotecc-request>
|2,200,21,1.3256060^22.214.10.2^SEP3CCE73ACBE00
After the OK:
14:49:26.317 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 22.212.126.35 on port 50108 index 227 with 442 bytes:
[21667404,NET]
SIP/2.0 200 OK
Via: SIP/2.0/TCP 22.214.10.18:5060;branch=z9hG4bKf63095b1b37b1
From: <sip:15026@22.214.10.18>;tag=435147058
To: <sip:15026@22.212.126.35>;tag=3cce73acbe00bd40ed051b81-4b2d068b
Call-ID: 2e587c80-1131b0e6-4ef59-120ad616@22.214.10.18
Date: Thu, 07 Feb 2013 13:49:17 GMT
CSeq: 101 REFER
Server: Cisco-CP7962G/9.3.1
Contact: <sip:855fe3cf-7528-67bc-3297-f7611620782d@22.212.126.35:50108;transport=TCP>
Content-Length: 0
|3,100,63,1.7871803^22.212.126.35^*
And thats the last messages with call ID starting by: 2e587c80
So could you say me how I can find the Transfer "destination" and why the call failled ?
Thanks,
Hervé Jacquemin
02-11-2013 02:21 AM
Please send the full logs. Include the called, calling number
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
02-11-2013 02:30 AM
Hello,
It's not possible, logs come from a financial institution, and I need to remove all the full E164 number from the logs (to much work).
But thanks for your help by the way
02-11-2013 02:32 AM
Unless we see the full picture we cant tell whats going on..Sorry. Even if you open a TAC case, you will need to send the full logs
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
08-16-2014 07:20 AM
Hi hjacquemin,
Have you solved this problem? I found the same thing with my customer. We are using
6921 with SIP Firmware. It is very weird that my IP Phone was hanged and must reset by unplug and plug.
Winai.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide