[cisco-voip] CallerName - H323 to CM 6.1(2)
Samuel Womack
samuel.womack1 at gmail.com
Tue Jan 27 16:28:56 EST 2009
How Easy/Hard would it be to try 12.4-11xw 6+; SAME
CONFIGS...Ensure the VOICE-CLASS is set on ur the Inbound Dial Peer
that Gets Chosen...
On Jan 27, 2009, at 3:21 PM, Carter, Bill wrote:
> I am trying to get inbound Caller Name from the Telco, to IP
> Phones. I have a couple of configuration issues/questions:
>
> CallManager 6.1(2), ISDN PRI, H323 gateway, IOS 12.4(20)T1
>
> Issue 1 – Do I need “isdn supp-service name calling” ?? (I’m sure I
> do, but caused problems for outbound Toll-Free calls)
>
> 1. With “isdn supp-service name calling” – Inbound caller name
> does not display on the phone. Outbound Toll-Free calls fail.
> 2. Without “isdn supp-service name calling” – Inbound caller
> name does not display on the phone. Outbound Toll-Free calls succeed.
>
> Issue 2 – See Caller Name on the Gateway, not passing to CM/IP Phones
> http://www.cisco.com/en/US/partner/docs/ios/voice/cube/configuration/guide/vb-gw-cm.html#wp1324664
>
> Calling name display information can be populated in ISDN messages
> in the Display Information Element (IE) of a Q.931 Setup or Notify
> message, or in the Facility IE of a Q.931 Setup or Facility message.
>
> Cisco Unified Communications Manager (Cisco Unified CM) interprets
> calling name information (for purposes of name display on IP phones
> registered with Unified CM only in the Display IE of the H.323 Setup
> and Notify messages. Name display information delivered in an H.323
> Facility message is not interpreted by Cisco Unified CM. Some ISDN
> switch types (for example, NI2) send a "name-to-follow" indication
> in the Q.931 Setup message and deliver the calling name subsequently
> in the Facility IE of a Q.931 Facility message. When a Cisco IOS
> gateway is connected to such an ISDN switch and interoperating with
> Cisco Unified CM by using the H.323 protocol, Cisco Unified CM is
> unable to display calling names on IP phones.
>
> H.323 Calling Name Display Without Buffering
> H.323 Calling Name Display With Buffering
>
> This is configured with:
> Voice service voip
> H323
> H225 display-ie ccm-compatible
> H225 timeout ntf # (to enable buffering)
>
> From the ISDN Q931 debugs I appear to get a “name-to-follow” type
> message.
>
> Jan 27 12:49:59: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8 callref =
> 0x0088
> Bearer Capability i = 0x8090A2
> Standard = CCITT
> Transfer Capability = Speech
> Transfer Mode = Circuit
> Transfer Rate = 64 kbit/s
> Channel ID i = 0xA98382
> Exclusive, Channel 2
> Facility i = 0x9F8B0100A10F02010106072A8648CE1500040A0100
> Protocol Profile = Networking Extensions
> 0xA10F02010106072A8648CE1500040A0100
> Component = Invoke component
> Invoke Id = 1
> Operation = InformationFollowing
> (calling_name)
> Name information in subsequent
> FACILITY message
> Calling Party Number i = 0x2183, '2174155513'
> Plan:ISDN, Type:National
> Called Party Number i = 0x80, '1011'
> Plan:Unknown, Type:Unknown
> Jan 27 12:49:59: ISDN Se0/2/0:23 Q931: Received SETUP callref =
> 0x8088 callID = 0x0082 switch = primary-ni interface = User
> Jan 27 12:49:59: ISDN Se0/2/0:23 Q931: TX -> CALL_PROC pd = 8
> callref = 0x8088
> Channel ID i = 0xA98382
> Exclusive, Channel 2
> Jan 27 12:49:59: ISDN Se0/2/0:23 Q931: TX -> ALERTING pd = 8
> callref = 0x8088
> Jan 27 12:49:59: ISDN Se0/2/0:23 Q931: RX <- FACILITY pd = 8
> callref = 0x0088
> Facility i =
> 0x9F8B0100A117020101020100800F4341525445522057494C4C49414D20
> Protocol Profile = Networking Extensions
> 0xA117020101020100800F4341525445522057494C4C49414D20
> Component = Invoke component
> Invoke Id = 1
> Operation = CallingName
> Name Presentation Allowed Extended
> Name = CARTER WILLIAM
>
>
>
>
> ~*~*~*~*~*~*~*~*~*~*~*~*
> Bill Carter
> Senior Network Analyst
> CCIE 5022
> Sentinel Technologies, Inc
> bcarter at sentinel.com
> SNR: 217.391.5015
> ~*~*~*~*~*~*~*~*~*~*~*~*
>
> _______________________________________________
> 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/20090127/83385973/attachment.html>
More information about the cisco-voip
mailing list