[cisco-voip] Configure incoming CLID on isdn of a 2821
Leetun, Rob
rleetun at bouldercounty.org
Thu May 20 12:01:47 EDT 2010
Here is new information on this problem:
The vendor who installed the ShoreTel system that is connected to our Cisco system via a H323 gateway, states that they have another customer whose caller id from ShoreTel does not work with a Cisco Callmanager environment. Hmmm???
ShoreTel states it is a Cisco problem.
Here is the latest debug for you to decide who should be doing what?
First call: from 3866 to 1670
Second call: from 1670 to 3866
_________________
debug isdn q931 is:
May 20 08:43:17.366: ISDN Se0/2/0:23 Q931: Applying typeplan for sw-type 0xD is 0x0 0x0, Calling num 3866
May 20 08:43:17.370: ISDN Se0/2/0:23 Q931: Applying typeplan for sw-type 0xD is 0x0 0x0, Called num 1670
May 20 08:43:17.370: ISDN Se0/2/0:23 Q931: TX -> SETUP pd = 8 callref = 0x72CD
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x9F8B0100A112020148020100800A526F62204C656574756E
jcphg2#
Protocol Profile = Networking Extensions
0xA112020148020100800A526F62204C656574756E
Component = Invoke component
Invoke Id = 72
Operation = CallingName
Name Presentation Allowed Extended
Name = Rob Lee
Calling Party Number i = 0x0081, '3866'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '1670'
Plan:Unknown, Type:Unknown
May 20 08:43:17.390: ISDN Se0/2/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xF2CD
Channel ID i = 0xA98381
Exclusive, Channel 1
May 20 08:43:17.486: ISDN Se0/2/0:23 Q931: RX <- ALERTING pd = 8 callref = 0xF2CD
jcphg2#
May 20 08:43:19.858: ISDN Se0/2/0:23 Q931: RX <- CONNECT pd = 8 callref = 0xF2CD
May 20 08:43:19.862: %ISDN-6-CONNECT: Interface Serial0/2/0:0 is now connected to 1670 N/A
jcphg2#
May 20 08:43:19.862: ISDN Se0/2/0:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x72CD
jcphg2#
May 20 08:43:35.255: ISDN Se0/2/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0xF2CD
Cause i = 0x8090 - Normal call clearing
May 20 08:43:35.259: %ISDN-6-DISCONNECT: Interface Serial0/2/0:0 disconnected from 1670 , call lasted 15 seconds
jcphg2#
May 20 08:43:35.259: ISDN Se0/2/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x72CD
May 20 08:43:35.275: ISDN Se0/2/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0xF2CD
jcphg2#
May 20 08:43:38.079: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8 callref = 0x00AE
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 = 0x9FAA068001008201008B0100A1190201360201008211422044656C61726F73612D43616D706F73
Protocol Profile = Networking Extensions
0x0100
0x820100
0x8B0100
0xA1190201360201008211422044656C61726F73612D43616D706F73
Component = Invoke component
Calling Party Number i = 0x00A0, '1670'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '3866'
Plan:Unknown, Type:Unknown
jcphg2#
May 20 08:43:38.095: ISDN Se0/2/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x80AE
Channel ID i = 0xA98397
Exclusive, Channel 23
May 20 08:43:38.227: ISDN Se0/2/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x80AE
Progress Ind i = 0x8188 - In-band info or appropriate now available
jcphg2#
May 20 08:43:41.279: %ISDN-6-CONNECT: Interface Serial0/2/0:22 is now connected to 1670 N/A
jcphg2#
May 20 08:43:41.279: ISDN Se0/2/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x80AE
May 20 08:43:41.295: ISDN Se0/2/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x00AE
jcphg2#
May 20 08:43:44.171: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8 callref = 0x00AF
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98396
Exclusive, Channel 22
Facility i = 0x9FAA068001008201008B0100A11B02013702010082134A61637175656C696E6520426561756C696575
Protocol Profile = Networking Extensions
0x0100
0x820100
0x8B0100
0xA11B02013702010082134A61637175656C696E6520426561756C696575
Component = Invoke component
Calling Party Number i = 0x00A0, '1234'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '4567'
Plan:Unknown, Type:Unknown
May 20 08:43:44.187: ISDN Se0/2/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x80AF
Channel ID i = 0xA98396
Exclusive, Channel 22
May 20 08:43:44.319: ISDN Se0/2/0:23 Q931: TX -> ALERTING pd = 8 callref = 0x80AF
Progress Ind i = 0x8188 - In-band info or appropriate now available
jcphg2#
May 20 08:43:48.171: %ISDN-6-CONNECT: Interface Serial0/2/0:21 is now connected to 4741 N/A
jcphg2#
May 20 08:43:48.171: ISDN Se0/2/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x80AF
May 20 08:43:48.183: ISDN Se0/2/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x00AF
jcphg2#
May 20 08:43:56.467: %ISDN-6-DISCONNECT: Interface Serial0/2/0:22 disconnected from 1670 , call lasted 15 seconds
jcphg2#no
May 20 08:43:56.467: ISDN Se0/2/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x80AE
Cause i = 0x8290 - Normal call clearing
May 20 08:43:56.483: ISDN Se0/2/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x00AE
May 20 08:43:56.491: ISDN Se0/2/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x80AE
=================================================================
May 20 08:43:17.370: ISDN Se0/2/0:23 Q931: TX -> SETUP pd = 8 callref = 0x72CD
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Facility i = 0x9F8B0100A112020148020100800A526F62204C656574756E
<**************************** mt decode start ************************>
Facility Ie Data:
Interpretation APDU: Len: 01
discardAnyUnrecognizedInvokePdu
RoseAPDU InvokePDU: Len: 12
invokeId: 72
callingName:
namePresentationAllowedSimple: 80, Len: 0A ç================ presentation allowed
"Rob Lee"
The calls that we receive from Shortel are with presentation restricted. (see following)
May 20 08:43:38.079: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8 callref = 0x00AE
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 = 0x9FAA068001008201008B0100A1190201360201008211422044656C617
26F73612D43616D706F73
<**************************** mt decode start ************************>
Facility Ie Data:
Network Facility Extension: Len: 06
sourceEntity: endPINX
destinationEntity: endPINX
Interpretation APDU: Len: 01
discardAnyUnrecognizedInvokePdu
RoseAPDU InvokePDU: Len: 19
invokeId: 54
callingName:
namePresentationRestrictedSimple: 82, Len: 11 ç===============presentation restricted
"B Del-Camo"
"s"
***********************2nd Call we receive from Shortel***********************
ay 20 08:43:44.171: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8 callref = 0x00AF
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98396
Exclusive, Channel 22
Facility i = 0x9FAA068001008201008B0100A11B02013702010082134A61637175656
C696E6520426561756C696575
<**************************** mt decode start ************************>
Facility Ie Data:
Network Facility Extension: Len: 06
sourceEntity: endPINX
destinationEntity: endPINX
Interpretation APDU: Len: 01
discardAnyUnrecognizedInvokePdu
RoseAPDU InvokePDU: Len: 1B
invokeId: 55
callingName:
namePresentationRestrictedSimple: 82, Len: 13 ç======================presentation restricted
"Jac Bul"
"ieu"
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Leetun, Rob
Sent: Wednesday, May 19, 2010 10:15 AM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Configure incoming CLID on isdn of a 2821
Hi Ryan,
Here is what the Cisco TAC saw:
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 = Rob Leetun
Display i = 'Rob Leetun'
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
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; 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
(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 for fast assistance!
From: 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
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] On Behalf Of Leetun, Rob
Sent: Wednesday, April 28, 2010 11:41 AM
To: 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
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100520/6d8d6695/attachment.html>
More information about the cisco-voip
mailing list