[cisco-voip] Calling Name (inbound and outbound) not workingon3640
and NM-HDV-2MFT-T1 48, Facility IE
Wes Sisk
wsisk at cisco.com
Wed Mar 9 15:25:55 EST 2005
Hi Adam,
Correct, the naam feature on IOS would have the voice gateway hold the
h323 setup msg for the call until the subsequent facilityIE is received
from the carrier on the pots leg, then IOS would send one setup complete
with displayIE over to CM. At least this was the last incarnation I
heard of the feature. This way no changes were required on CM. As it
is not implemented yet, this is a no go. Sorry, MGCP is still the only
option.
MGCP and h323 dial-peers can co-exist. However, they cannot very well
control the same voice port. MGCP becomes the default application if
both h323 and mgcp configs are present (after CSCeb08888 is fixed.
before this, it's whichever appears first in the config). So your
inbound calls would always be routed by MGCP. If you are using different
call signaling on different voice ports then all is well.
/Wes
Blomfield, Adam wrote:
>Here's the response from opening a TAC case...
>
>"In the h323 protocol the call manager can't understand the calling name
>in the Facility IE. The PSTN/PBX has to send us the calling name in the
>Display IE. These are the two fields which comes in an isdn q931 setup
>message. The CM can understand the calling name in Facility IE if we are
>running MGCP protocol.
>
>In order to get the caller name displayed on the IP Phone we need to get
>the caller name in the display ie field of the Isdn q931 call setup
>message. This can only be configured on the telco switch. You will have
>to ask your telephone company/service provider to enable sending of
>display ie in the call setup message."
>
>Looks like another case of forgoing standards and doing it 'the Cisco
>way'.
>
>If I have a bunch of dial peers in my config that point to other
>services for things like T.37 onramp faxing how would they be affected
>by moving to MGCP. Can MGCP and dial-peers happily coexist
>simultaneously in the same config? I know that you can have backup
>dial-peers that go into effect if CM fails and you go into SRST but I'm
>not sure about the live coexistence.
>
>Thanks,
>Adam
>
>-----Original Message-----
>From: Wes Sisk [mailto:wsisk at cisco.com]
>Sent: Wednesday, March 09, 2005 11:51 AM
>To: Blomfield, Adam
>Cc: cisco-voip at puck.nether.net
>Subject: [SPAM] - Re: [cisco-voip] Calling Name (inbound and outbound)
>not workingon3640 and NM-HDV-2MFT-T1 48, Facility IE - Email found in
>subject
>
>Adam,
>
>Looks like the feature may have been integrated in 12.3T. Start with
>'isdn supp-service name calling' and go from there. It is part of a
>feature that originally targeted SIP but then expanded to h323. Not
>sure if the full h323 implementation is available yet. A good question
>for a formal TAC case or your Cisco SE.
>
>/Wes
>
>Blomfield, Adam wrote:
>
>
>
>>I have a similar setup to this... my gateway is a 3662 running IOS
>>12.3(11)T3. I had my trunks changed from 5eSS to NI2 last night and I
>>
>>
>am
>
>
>>now getting calling name delivered into the Facilities IE and can see
>>this information in a Q931 debug as shown below. The gateway is
>>connected to CCM via H.323 and I am not trying to configure it so that
>>the name is passed onto the phone handsets, however I cannot see any
>>
>>
>way
>
>
>>to get CallManager to looked at the Facility IE on a H.323 gateway. Is
>>it possible or do I have to migrate to MGCP to get this functionality?
>>
>>Thanks,
>>Adam
>>_________________________________________
>>
>>Adam Blomfield
>>WAN Administrator
>>Information Technology
>>Sulzer Chemtech USA, Inc.
>>4019 South Jackson Avenue, Tulsa OK 74107
>>Tel. +1 918-445-6642, Fax +1 918-446-4701
>>Cell +1 918-625-1739
>>E-Mail mailto:adam.blomfield at sulzer.com
>>Internet http://www.sulzerchemtech.com
>>_________________________________________
>>
>>-----Original Message-----
>>From: cisco-voip-bounces at puck.nether.net
>>[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of William M.
>>Sandiford
>>Sent: Wednesday, March 02, 2005 9:35 AM
>>To: cisco-voip at puck.nether.net
>>Subject: RE: [cisco-voip] Calling Name (inbound and outbound) not
>>workingon3640 and NM-HDV-2MFT-T1 48, Facility IE
>>
>>Hello:
>>
>>Just a quick note for all that were following this thread and that have
>>helped out, I was able to get the problem totally solved. I'm posting
>>this for reference / archive purposes in case others have this problem
>>in the future.
>>
>>The problem was that my carrier (TELUS) passes the calling name as a
>>Facility IE as opposed to a Display IE. On my platform (3640), and
>>
>>
>most
>
>
>>others I presume, calling name by facility IE was not supported until
>>IOS 12.3(4)T so you will need that or later to make it work (I used
>>12.3(11)T3). The following configuration items were required in
>>addition to any other configs that you already have.
>>
>>Under the serial interface for your T1, in my case int Serial3/0:23
>>
>>Interface Serial3/0:23
>>isdn supp-service name calling
>>isdn outgoing ie facility
>>no isdn outgoing display-ie
>>!
>>
>>Thanks to everyone who pointed me in the right direction for all the
>>help.
>>
>>Regards,
>>Bill
>>
>>
>>-----Original Message-----
>>From: William M. Sandiford
>>Sent: Tuesday, March 01, 2005 4:57 PM
>>To: Mark R. Lindsey; cisco-voip at puck.nether.net
>>Subject: RE: [cisco-voip] Calling Name (inbound and outbound) not
>>working on3640 and NM-HDV-2MFT-T1 48
>>
>>
>>Ok
>>
>>So I finally got the calling name into the q931 trace as a facility
>>message. It turns out that Calling name as a facility IE message
>>
>>
>wasn't
>
>
>>supported until 12.3(4)T so I had to upgrade to a newer version of IOS.
>>That being said. Now I am seeing the calling name in the trace, but it
>>still isn't making it into the sip message.
>>
>>Any suggestions?
>>
>>Bill
>>
>>
>>00:08:52: ISDN Se3/0:23 Q931: RX <- SETUP pd = 8 callref = 0x03C9
>> Bearer Capability i = 0x8090A2
>> Standard = CCITT
>> Transer Capability = Speech
>> Transfer Mode = Circuit
>> Transfer Rate = 64 kbit/s
>> Channel ID i = 0xA98381
>> Exclusive, Channel 1
>> Facility i =
>>0x9F8B0100A117020101020100800F43414E444E20444F4D41494E204E41
>> Protocol Profile = Networking Extensions
>> 0xA117020101020100800F43414E444E20444F4D41494E204E41
>> Component = Invoke component
>> Invoke Id = 1
>> Operation = CallingName
>> Name presentation allowed
>> Name = THE NAME
>> Progress Ind i = 0x8283 - Origination address is non-ISDN
>> Calling Party Number i = 0x2183, 'XXXXXX6814'
>> Plan:ISDN, Type:National
>> Called Party Number i = 0xA1, 'XXXXXX2000'
>> Plan:ISDN, Type:National
>>00:08:52: ISDN Se3/0:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x83C9
>> Channel ID i = 0xA98381
>> Exclusive, Channel 1
>>00:08:52: ISDN Se3/0:23 Q931: TX -> CONNECT pd = 8 callref = 0x83C9
>>00:08:52: ISDN Se3/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref =
>>
>>
>0x03C9
>
>
>>00:08:56: ISDN Se3/0:23 Q931: RX <- DISCONNECT pd = 8 callref = 0x03C9
>>
>>
>
>
>
>> Cause i = 0x8090 - Normal call clearing
>>00:08:56: ISDN Se3/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x83C9
>>00:08:57: ISDN Se3/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref =
>>
>>
>0x03C
>
>
>>
>>-----Original Message-----
>>From: Mark R. Lindsey [mailto:lindsey at e-c-group.com]
>>Sent: Tuesday, March 01, 2005 11:29 AM
>>To: William M. Sandiford
>>Cc: cisco-voip at puck.nether.net
>>Subject: Re: [cisco-voip] Calling Name (inbound and outbound) not
>>working on 3640 and NM-HDV-2MFT-T1 48
>>
>>
>>On Mar 1, 2005, at 11:20 AM, William M. Sandiford wrote:
>>
>>
>>
>>
>>
>>>So it looks like I'm going to have to go off of mainline and on to T
>>>in order to get this to work?
>>>
>>>
>>>
>>>
>>I think so. But even in those, we've helped Cisco identify some issues
>>--
>>
>>CSceg80858 -- Remote-Party-ID is formatted wrong/oddly in current
>>releases (to be addressed in 12.4)
>>
>>CSCsa67646 -- SIP "486 Busy Here" messages aren't returned on some
>>SIP-PSTN calls
>>
>>---
>>Mark R. Lindsey, ECG
>>+1-229-316-0013 lindsey at e-c-group.com
>>
>>
>>
>>
>>
>>
More information about the cisco-voip
mailing list