[cisco-voip] Configure incoming CLID on isdn of a 2821

Nate VanMaren VanMarenNP at ldschurch.org
Wed May 12 11:24:55 EDT 2010


Rob,

Calling name display in the facility IE was added in 12.4(11)XW, then brought into the main T line in 12.4(20)T.  http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-cm.html#wp1295243

http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-cm.html#wp1315365

I have gateways running 12.4(11)XW3 and 124-24.T1 that are working great.

If you can't upgrade IOS, you can switch to MGCP to get calling name in facility IE to work.

-Nate

From: Leetun, Rob [mailto:rleetun at bouldercounty.org]
Sent: Wednesday, May 12, 2010 9:09 AM
To: Nate VanMaren
Cc: Barger, Joe
Subject: RE: [cisco-voip] Configure incoming CLID on isdn of a 2821

Hi Nate,

We are using h.323.

Thanks.

Rob

From: Nate VanMaren [mailto:VanMarenNP at ldschurch.org]
Sent: Tuesday, May 11, 2010 4:42 PM
To: Leetun, Rob; Barger, Joe
Subject: RE: [cisco-voip] Configure incoming CLID on isdn of a 2821

Is this a MGCP or a h.323 gateway?

Sending calling name in facility IE is pretty common from a telco, but it's fairly recent that h.323 gateways to understand that(2 years?).  MGCP has been able to do it for a while.
-Nate

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Leetun, Rob
Sent: Tuesday, May 11, 2010 4:32 PM
To: Ryan Ratliff; Barger, Joe
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Configure incoming CLID on isdn of a 2821

The blindhog link helped but the h225 display-ie ccm-compatible is not available in the version of software on the gateway.  I have been working with TAC and this what they said:


After checking all the information we have gathered, it appears that the Telco is not sending the IE in the proper format for the Call manager to interpret what the gateway send, so we may require contact the Telco to request the following.



The Telco may send the Information Element as a subsequent facility Display IE element Instead of using FACILITY.



Here is an example of how the Information Element should be send to the call manager:



Facility i = 0x9F8B0100A11202013E020100800A526F62204C656574756E

                Protocol Profile =  Networking Extensions

                0xA11202013E020100800A526F62204C656574756E

                Component = Invoke component

                        Invoke Id = 62

                        Operation = CallingName

                                Name Presentation Allowed Extended

                                Name = Bill Bass

        Display i = 'Bill Bass'

        Calling Party Number i = 0x0081, '3866'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '1670'

                Plan:Unknown, Type:Unknown



This was capture from a call that was coming from the call manager and that is what is required.





The Telco is currently sending the following IE:



Facility i =

0x9FAA068001008201008B0100A1190201530201008211422044656C61726F73612D43616D706F73



                Protocol Profile =  Networking Extensions

                0x0100

                0x820100

                0x8B0100

                0xA1190201530201008211422044656C61726F73612D43616D706F73

                Component = Invoke component

        Calling Party Number i = 0x00A0, '1670'

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0x80, '3866'

                Plan:Unknown, Type:Unknown





Please let me know if you could contact the Telco or conference in the

Telco to request this information from their side.


From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Wednesday, April 28, 2010 3:27 PM
To: Barger, Joe
Cc: Matthew Loraditch; Leetun, Rob; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Configure incoming CLID on isdn of a 2821

So your name is in the facility.  You need to check out the CCM traces where the full thing will be decoded and you can see what number is there.

-Ryan

On Apr 28, 2010, at 5:25 PM, Barger, Joe wrote:

Yeah that is the weird part we are seeing the name even though you don't see it incoming  in the debug...

From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Wednesday, April 28, 2010 2:48 PM
To: Matthew Loraditch
Cc: Leetun, Rob; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>; Barger, Joe
Subject: Re: [cisco-voip] Configure incoming CLID on isdn of a 2821

I believe if there is a number in the facility it will override that in the calling number IE.  You can look at CCM traces to see if we are decoding the facility.

-Ryan

On Apr 28, 2010, at 4:14 PM, Matthew Loraditch wrote:

Well you aren't getting calling name and the number you are getting appears to be private, is this a telco pri or a private link?  albeit regardless you should be getting the number to come through to the phones unless you have something in CCM or your dial-peers altering it.


Matthew Loraditch, CCNA, CCDA
1965 Greenspring Drive
Timonium, MD 21093
support at heliontechnologies.com<mailto:support at heliontechnologies.com>
(p) (410) 252-8830
(F) (443) 541-1593

Visit us at www.heliontechnologies.com<http://www.heliontechnologies.com/>
Support Issue? Email support at heliontechnologies.com<mailto:support at heliontechnologies.com> for fast assistance!

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Leetun, Rob
Sent: Wednesday, April 28, 2010 2:33 PM
To: Leetun, Rob; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Cc: Barger, Joe
Subject: Re: [cisco-voip] Configure incoming CLID on isdn of a 2821

Here is the Debug isdn q931

Apr 28 12:14:43.243: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8  callref = 0x001B
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98397
                Exclusive, Channel 23
        Facility i = 0x9FAA068001008201008B0100A11802011C0201008210416E64726561204672616E636973636F
                Protocol Profile =  Networking Extensions
                0x0100
                0x820100
                0x8B0100
                0xA11802011C0201008210416E64726561204672616E636973636F
                Component = Invoke component
        Calling Party Number i = 0x00A0, '4718'
                Plan:Unknown, Type:Unknown
        Called Party Number i = 0x80, '3579'
                Plan:Unknown, Type:Unknown
Apr 28 12:14:43.259: ISDN Se0/2/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0x801B
        Channel ID i = 0xA98397
                Exclusive, Channel 23
Apr 28 12:14:43.395: ISDN Se0/2/0:23 Q931: TX -> ALERTING pd = 8  callref = 0x801B
        Progress Ind i = 0x8188 - In-band info or appropriate now available
Apr 28 12:14:47.907: %ISDN-6-CONNECT: Interface Serial0/2/0:22 is now connected to 4718 N/A
Apr 28 12:14:47.907: %ISDN-6-CONNECT: Interface Serial0/2/0:22 is now connected to 4718 N/A
Apr 28 12:14:47.907: ISDN Se0/2/0:23 Q931: TX -> CONNECT pd = 8  callref = 0x801B
Apr 28 12:14:47.923: ISDN Se0/2/0:23 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x001B
Apr 28 12:14:56.051: ISDN Se0/2/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0x001B
        Cause i = 0x8090 - Normal call clearing
Apr 28 12:14:56.051: %ISDN-6-DISCONNECT: Interface Serial0/2/0:22  disconnected from 4718 , call lasted 8 seconds
Apr 28 12:14:56.055: ISDN Se0/2/0:23 Q931: TX -> RELEASE pd = 8  callref = 0x801B
Apr 28 12:14:56.067: ISDN Se0/2/0:23 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x001B


From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Leetun, Rob
Sent: Wednesday, April 28, 2010 11:41 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Configure incoming CLID on isdn of a 2821

Hi,

I cannot get incoming CLID to be presented on the phone.  We have a 2821 with isdn.  Does anyone know of a command I can use to get this to work?

Thanks!


Rob

Robert Leetun
Network Engineer
Boulder County Information Technology
2025 14th Street
Boulder, CO 80302
303 441-3866 (W)
303 441-3983 (F)
rleetun at bouldercounty.org<mailto:arees at bouldercounty.org>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip




NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100512/cf5b701f/attachment.html>


More information about the cisco-voip mailing list