[cisco-voip] Alerting Name being passed to PBX
Tim Smith
thsglobal at gmail.com
Thu Aug 7 01:50:25 EDT 2008
I'm trying to remember exactly.. but I would think there should be some
Q.SIG IE's stuck in there...
I think MGCP / Q.SIG will just send Calling name through the Facility IE
anyway.. I think we should see some extra jazz in that debug.
Your 100% sure its not routing to the NEC based on an old route pattern /
route list (that is still H323 not Q.SIG?)
What does a call from the NEC to CCM look like?
I think we should see a Q.SIG facility or Remote Operations Protocol message
with something in there.
There is a "Triple Combo Tool" written by one of the Cisco guys that can
decode these.
Cheers,
Tim.
On 8/7/08, William Roy <William.Roy at l7.com.au> wrote:
>
> Answers inline...
>
> So thats a call from CCM to NEC...
>
> Yes that was a call from CCM to NEC
>
> Where do you have the calling names filled in on the phone config?
> Do you have both Display and Alerting name set on the line? (normal and
> ASCII?)
>
> Yes have Display and Alerting set for both normal and Ascii
>
> Calling party settings on the gateway itself?
>
> Calling Party Presentation - Allowed Calling Party Selection -
> Originator
> Called party IE Number - Unknown
> Calling party IE number - Unknown
> Called Numbering Plan - Cisco CallManager
> Calling Numbering Plan - Cisco CallManager
>
> Display IE Delivery is greyed out and can not be set
>
> Route patterns to the NEC set to offnet or on net?
>
> Currently set to onnet
>
> You dont have any route patterns / translation patterns in there doing
> any restriction on the calling opname?
>
> Nope
>
> GW is definitely MGCP and set to Q.SIG?
>
> Yes
>
>
>
> On 8/6/08, William Roy <William.Roy at l7.com.au> wrote:
>>
>> No we do not get connected name once the call is connected only calling
>> number. This is a debug from an IP phone to a NEC phone
>>
>>
>> ho-vgate-1#
>> ho-vgate-1#
>> *Aug 6 08:21:39.106: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref =
>> 0x001E
>> Sending Complete
>> Bearer Capability i = 0x8090A3
>> Standard = CCITT
>> Transfer Capability = Speech
>> Transfer Mode = Circuit
>> Transfer Rate = 64 kbit/s
>> Channel ID i = 0xA9839F
>> Exclusive, Channel 31
>> Calling Party Number i = 0x0081, '6005'
>> Plan:Unknown, Type:Unknown
>> Called Party Number i = 0x80, '4723'
>> Plan:Unknown, Type:Unknown
>> *Aug 6 08:21:39.166: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8
>> callref = 0x801E
>> Channel ID i = 0xA9839F
>> Exclusive, Channel 31
>> *Aug 6 08:21:39.170: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8 callref
>> = 0x801E
>> *Aug 6 08:21:43.158: ISDN Se0/0/0:15 Q931: RX <- CONNECT pd = 8 callref
>> = 0x801E
>> Progress Ind i = 0x8082 - Destination address is non-ISDN
>> Connected Number i = 0x0081, '4723'
>> *Aug 6 08:21:43.162: ISDN Se0/0/0:15 Q931: TX -> CONNECT_ACK pd = 8
>> callref = 0x001E
>>
>> ------------------------------
>> *From:* smithsonianwa at gmail.com [smithsonianwa at gmail.com] On Behalf Of
>> Tim Smith [thsglobal at gmail.com]
>> *Sent:* Wednesday, 6 August 2008 3:54 PM
>> *To:* William Roy
>> *Cc:* cisco-voip at puck.nether.net
>> *Subject:* Re: [cisco-voip] Alerting Name being passed to PBX
>>
>>
>> Hi Wil,
>>
>> What do you see with a debug isdn q931?
>>
>> Do you get connected name once the call is established?
>>
>> Cheers,
>>
>> Tim.
>>
>>
>>
>>
>>
>> On 8/6/08, William Roy <William.Roy at l7.com.au> wrote:
>>>
>>> I have NEC IPX2400 PBX connected to a ISR2851 via an QSIG E1 link. The
>>> ISR is setup as an MGCP gateway with a CUCM 6.1 cluster. I am not seeing
>>> Calling name being passed either from an NEC phone to a Cisco IP phone or
>>> visa versa. Is there any debug I can run on the ISR to see if the cisco ip
>>> phone is sending Calling name?
>>>
>>> regards
>>> Wil
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080807/200e6d56/attachment-0001.html>
More information about the cisco-voip
mailing list