[cisco-voip] Call Back

Tue May 2 10:12:59 EDT 2006

Nick,

In that case there is not much we can do. The extra FacilityIE is to 
notify the Ericsson that this call is the call for the previously 
requested callback. The Ericsson should accept this facilityIE.

If you do not make progress with Ericsson support you could modify the 
CM Service Parameter "Call Back Recall T3 Timer (sec)" to a value lower 
than the default 20 seconds.

/Wes

Nick Kassel wrote:
> Wes
> I have tested this and it works fine anything after 20 seconds, sounds 
> like the facility IE is causing the problem. I have not logged a TAC 
> case yet, should I still log one?
> Regards
> Nick
>
> ------------------------------------------------------------------------
> *From:* Wes Sisk [mailto:wsisk at cisco.com]
> *Sent:* Monday, May 01, 2006 6:57 PM
> *To:* Nick Kassel
> *Subject:* Re: [cisco-voip] Call Back
>
> Nick,
>
> After the callback message appears wait 38 seconds the press the dial 
> key. That should timeout the callback and CM will send SETUP without 
> the extra facilityIE. This will confirm if it is the facilityIE 
> causing the problem.
>
> Did you open a TAC SR for this?
>
> /Wes
>
> Nick Kassel wrote:
>>
>> I have tried this again and if I select the primary line of the phone 
>> and dial the number then it will not go through either, the same 
>> issue occurs, however if I try it and select a shared line on the 
>> phone then dial the number it works ok.
>>
>> We do not have these calls routing through a translation pattern.
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Wes Sisk [mailto:wsisk at cisco.com]
>> *Sent:* Friday, April 28, 2006 2:55 PM
>> *To:* Nick Kassel
>> *Subject:* Re: [cisco-voip] Call Back
>>
>> I suspect your pbx may not like the extra facilityIE we send when we 
>> attempt the callback.
>> can you test once more, and when you get the callback notification 
>> press a line button on the right side of the phone to go offhook and 
>> attempt to dial 3432 directly? does that call go through? At this 
>> point will need to open a TAC case to pursue further.
>>
>> let's eliminate a few other things just to make sure:
>> does your initial call route through a translation pattern?
>>
>> /Wes
>>
>> Nick Kassel wrote:
>>
>> Hi Wes
>>
>> I have tried this again and it just does not seem to go anywhere, 
>> after I hit dial the phone says Call Proceed and the dialled number 
>> just sits on the display, I do not get any ring tone from the other 
>> end or hear any tone from the calling phone.
>>
>> I’m a bit stuck as what to do.
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Wes Sisk [mailto:wsisk at cisco.com]
>> *Sent:* Thursday, April 27, 2006 6:27 PM
>> *To:* Nick Kassel
>> *Cc:* cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>> *Subject:* Re: [cisco-voip] Call Back
>>
>> nope. that's not the problem.
>>
>> CM does present the call to the Mitel, only with 1 extra FacilityIE 
>> this time.
>>
>> Original call:
>> Outbound PRI SETUP message to 172.30.0.10 at timestamp 04/27/2006 
>> 10:31:21.130
>> SETUP, pd = 8, callref = 0x125A, Message Size = 63 bytes
>> Sending Complete
>> Bearer Capability i = 0x8090A3, ITU-T standard, Speech, Circuit mode, 
>> 64k, A-law
>> Channel ID i = 0xA98398 - PRI interface, Exclusive channel 24
>> Facility i = 
>> 0x9FAA06800100820100A113020101020100800B4E69636B204B617373656C, 
>> Facility code not parsed
>> Calling Party Number i = '6515' - Plan: Unknown, Type: Unknown, 
>> Presentation Allowed, User-provided, verified and passed
>> Called Party Number i = '3432' - Plan: Unknown, Type: Unknown
>>
>> CallBack notification to the Mitel:
>> Outbound PRI SETUP message to 172.30.0.10 at timestamp 04/27/2006 
>> 10:31:25.115
>> SETUP, pd = 8, callref = 0x125C, Message Size = 76 bytes
>> Sending Complete
>> Bearer Capability i = 0xA880, ISO/IEC standard, UDI, Circuit mode, 
>> Packet mode rate
>> Channel ID i = 0xAC - PRI interface, Exclusive channel 0
>> Facility i = 
>> 0x9FAA06800100820100A123020149020128301BA006800436353135800433343332400504038090A38C01008D01FF, 
>> Facility code not parsed
>> Calling Party Number i = '6515' - Plan: Unknown, Type: Unknown, 
>> Presentation Allowed, User-provided, verified and passed
>> Called Party Number i = '3432' - Plan: Unknown, Type: Unknown
>>
>> Outbound call to the mitel after you press dial:
>> Outbound PRI SETUP message to 172.30.0.10 at timestamp 04/27/2006 
>> 10:31:52.521
>> SETUP, pd = 8, callref = 0x125D, Message Size = 84 bytes
>> Sending Complete
>> Bearer Capability i = 0x8090A3, ITU-T standard, Speech, Circuit mode, 
>> 64k, A-law
>> Channel ID i = 0xA98397 - PRI interface, Exclusive channel 23
>> Facility i = 
>> 0x9FAA06800100820100A113020101020100800B4E69636B204B617373656C, 
>> Facility code not parsed
>> Facility i = 0x9FAA06800100820100A10802014A02011F0500, Facility code 
>> not parsed
>> Calling Party Number i = '6515' - Plan: Unknown, Type: Unknown, 
>> Presentation Allowed, User-provided, verified and passed
>> Called Party Number i = '3432' - Plan: Unknown, Type: Unknown
>>
>> Note the extra FacilityIE this time. However the Mitel responds as if 
>> it is processing the call:
>> Inbound PRI CALL_PROC message from 172.30.0.10 at timestamp 
>> 04/27/2006 10:31:52.631
>> CALL_PROC, pd = 8, callref = 0x925D, Message Size = 10 bytes
>> Channel ID i = 0xA98397 - PRI interface, Exclusive channel 23
>>
>> Mitel acknowledges the call and requests to cut through audio. 
>> Possibly for ringback tone?
>> Inbound PRI PROGRESS message from 172.30.0.10 at timestamp 04/27/2006 
>> 10:31:53.162
>> PROGRESS, pd = 8, callref = 0x925D, Message Size = 9 bytes
>> Progress Indicator i = 0x8188 - In-band info or appropriate now 
>> available
>>
>> Call rang for 10 seconds before you disconnected it. Are you sure 
>> nothing appeared on the PBX phone?
>> Outbound PRI DISCONNECT message to 172.30.0.10 at timestamp 
>> 04/27/2006 10:32:03.709
>> DISCONNECT, pd = 8, callref = 0x125D, Message Size = 9 bytes
>> Cause i = 0x8090 - Normal call clearing
>>
>> /Wes
>>
>> Wes Sisk wrote:
>>
>> Thanks Nick.
>>
>> Please open a TAC case and attach the CCM trace and the corresponding 
>> SDL trace from trace\sdl\ccm. I don't believe this should happen:
>> 10:31:25.099 CCM|CallBackManager - ERROR Can't Route ss = 0x500527b, 
>> ssOtherParty = 0x500527c|
>>
>> /Wes
>>
>> Nick Kassel wrote:
>>
>> Wes
>>
>> Sorry forgot to mention, I was calling from 6515 to 3432 (Ericsson 
>> MD110 DN), I set Call Back, when 3432 was available I received the 
>> notification on the phone and pressed dial and the number dialled but 
>> did not go anywhere is just sort of hung. I then hung up.
>>
>> Nick
>>
>> -----Original Message-----
>> *From:* Wes Sisk [mailto:wsisk at cisco.com]
>> *Sent:* 27 April 2006 15:09
>> *To:* Nick Kassel
>> *Cc:* cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>> *Subject:* Re: [cisco-voip] Call Back
>>
>> There are multiple setups in this trace. What is the calling/called 
>> party number for your specific call?
>>
>> /Wes
>>
>> Nick Kassel wrote:
>>
>> Hi Wes, I’m un sure about analysing the trace, could you possibly 
>> take a look and see if you can make out what is happening for me.
>>
>> Regards
>>
>> Nick
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Wes Sisk [mailto:wsisk at cisco.com]
>> *Sent:* Wednesday, April 26, 2006 4:03 PM
>> *To:* Nick Kassel
>> *Cc:* cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>> *Subject:* Re: [cisco-voip] Call Back
>>
>> check get the 'debug isdn q931' from the gateway or check the CM 
>> traces to see what goes south with the signaling during call setup.
>>
>> /Wes
>>
>> Nick Kassel wrote:
>>
>> We currently have our CCM cluster linked to an Ericsson MD110 PBX via 
>> Qsig. I have added the Call Back softkey to my phone and if I place a 
>> call to a phone on the Ericsson and then activate Call Back, I 
>> receive the information that the DN on the Ericsson is now available 
>> but when I hit the dial key, the call will not connect, it dials the 
>> number but does not go through and it says on the display Call 
>> Proceed and sits there.
>>
>> Any one come across any issues like this before?
>>
>