[cisco-voip] Configure incoming CLID on isdn of a 2821
Ryan Ratliff
rratliff at cisco.com
Wed Apr 28 16:47:59 EDT 2010
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
> 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
>
> _______________________________________________
> 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/20100428/00aaf6c2/attachment.html>
More information about the cisco-voip
mailing list