[cisco-voip] Inbound Caller Name

Voll, Scott Scott.Voll at wesd.org
Mon Mar 7 12:20:12 EST 2005


For once NO........  YAAAAAAA

Scott

-----Original Message-----
From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Monday, March 07, 2005 9:18 AM
To: Voll, Scott
Cc: Walenta, Phil; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Inbound Caller Name

That is also known as ni3 encoing where cname is sent down in a facility

IE.  CM supports this with MGCP gateways.  I do not recall where we 
stand on h323 support.  Let me guess, you need h323?

/Wes

Voll, Scott wrote:

>My Telco says that it needs to be "Telcordia (Bell Core) Specification
>GR1367-core" compliant?  Does CM comply?
>
>Scott
>
>-----Original Message-----
>From: Walenta, Phil [mailto:philip.walenta at berbee.com] 
>Sent: Tuesday, March 01, 2005 2:21 PM
>To: Voll, Scott; cisco-voip at puck.nether.net
>Subject: RE: [cisco-voip] Inbound Caller Name
>
>Inbound caller name is generally available wherever you can get a PRI.
>It's simply a matter of getting the phone company to understand and
>activate what you want.  I've had this particular feature working in at
>least 10 different states. 
>
>-----Original Message-----
>From: Voll, Scott [mailto:Scott.Voll at wesd.org] 
>Sent: Tuesday, March 01, 2005 4:20 PM
>To: Walenta, Phil; Carter, Bill; cisco-voip at puck.nether.net
>Subject: RE: [cisco-voip] Inbound Caller Name
>
>When they are talking about inbound caller name, you mean you can get
>the name of the person calling and the number?  I'll I have is the
>number calling?  Is this a service provided by the telco?  Does anyone
>know if you can get that in Oregon?
>
>Scott
>
>-----Original Message-----
>From: cisco-voip-bounces at puck.nether.net
>[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Walenta, Phil
>Sent: Tuesday, March 01, 2005 10:08 AM
>To: Carter, Bill; cisco-voip at puck.nether.net
>Subject: RE: [cisco-voip] Inbound Caller Name
>
>Unless something has changed recently, inbound caller name won't work
>with H.323.  Something about not being able to pass the facility IE
info
>over to the appropriate place in H.323.  
>
>BTW, the calling name is listed below, you just need to decode the
>facility IE field.  I'd swear at one time there was a tool posted on
CCO
>to completely debug the q.931 messages but my searches can't seem to
>find it. 
>
>-----Original Message-----
>From: cisco-voip-bounces at puck.nether.net
>[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Carter, Bill
>Sent: Tuesday, March 01, 2005 11:01 AM
>To: cisco-voip at puck.nether.net
>Subject: [cisco-voip] Inbound Caller Name
>
>It appears I am CallerID Name from Telco, but CallManager is not
>displaying this on the phones.  I am using a H323 Gateway and CCM
>3.3(4)SR01.
>
>On the CCM Gateway configuration page, I have "Display IE Delivery"
>checked.  Since this is under "Outbound Calls" I don't know if this
>applies to inbound Caller name.
>
>How can I get calling party name to pass to the IP Phones?
>
>        Bearer Capability i = 0x8090A2
>                Standard = CCITT
>                Transer Capability = Speech
>                Transfer Mode = Circuit
>                Transfer Rate = 64 kbit/s
>        Channel ID i = 0xA98383
>                Exclusive, Channel 3
>        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, 'XXXXXXXXXX'
>                Plan:ISDN, Type:National
>        Called Party Number i = 0x80, '0811'
>                Plan:Unknown, Type:Unknown
>        Channel ID i = 0xA98383
>                Exclusive, Channel 3
>        Progress Ind i = 0x8188 - In-band info or appropriate now
>available Mar  1 10:43:24.742: ISDN Se2/0:23 Q931: RX <- FACILITY pd =
8
>callref = 0x4F31
>
>        Facility i =
>0x9F8B0100A117020101020100800F535052494E474649454C4420434C4
>9
>                Protocol Profile =  Networking Extensions
>                0xA117020101020100800F535052494E474649454C4420434C49
>                Component = Invoke component
>                        Invoke Id = 1
>                        Operation = CallingName
>                                Name presentation allowed
>                                Name = MY NAME
>
>_______________________________________________
>cisco-voip mailing list
>cisco-voip at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-voip
>
>_______________________________________________
>cisco-voip mailing list
>cisco-voip at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-voip
>
>_______________________________________________
>cisco-voip mailing list
>cisco-voip at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-voip
>  
>



More information about the cisco-voip mailing list