[cisco-voip] Caller Name ID possible via Facility IE with H.323?

[Wes Sisk]

it was implemented for SIP, but not for h323 because of some  
interesting challenges with the way h323 calls are set up.

/Wes
On Dec 15, 2005, at 9:07 PM, Brian Feeny wrote:

Thanks, I have a case open, but I am wanting a clear explanation of  
the "isdn supp-service name calling", and how it applies, if at all  
to H.323.

I am going to try to get Hellsouth to switch to Display IE, but I am  
not holding my breath.

Brian

On Thursday, December 15, 2005, at 07:22PM, Bell, Joe  
<Joe_Bell at adp.com> wrote:

> Brian,
>
> Unless someone knows any pfm, there is no way to accomplish caller- 
> id on
> a PRI with H.323 unless your provider switches the data into  
> Display IE
> (good luck with that).  Recently (using 12.4(4T), I opened a TAC case
> about this issue to see if there was any way to accomplish this or  
> if it
> had been addressed in the new 12.4 train.  TAC sent me a clear answer
> saying H.323 and caller-id are unsupported and in order to get it, I
> needed to go to MGCP.
>
> Joe Bell
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Brian Feeny
> Sent: Thursday, December 15, 2005 11:23 AM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] Caller Name ID possible via Facility IE with
> H.323?
>
>
> I have read the thread:
>
> https://puck.nether.net/pipermail/cisco-voip/2005-March/003509.html
>
> And was curious as to the outcome.  I have PRI's coming in from a  
> 5ESS,
> and the carrier is sending the ID in the facility IE (inbound calls to
> us), and of course CM appears to want it in the display IE.  I have  
> read
> of ways CM would take it via the Facility ID if using MGCP AND  
> NI2/3 or
> MGCP AND QSIG.  Does any solution at all exist for H.323?  I have  
> tried
> to set my switch type for NI and QSIG, both work as far as
> placing/receiving calls, but I still cannot get inbound name id.  I  
> have
> tried to set "isdn supp-service name calling" on the gateway as  
> well but
> it doesn't seem to fix it.  Gateways are running late 12.3T code,  
> CM is
> 4.1(3)SR2.
>
> Sure I can try to battle it out with Bellsouth and ask them to  
> change to
> display IE, but I am sure they will not do it for me, I'll try though.
> But I am hoping there is a solution for those of us with H.323  
> links.  I
> could possibly get them to switch the circuit to NI2 or QSIG.  Like I
> said switching the switch type on the gateway works, without having  
> the
> carrier do anything probably because its just compatible, but not sure
> if formally having them change the switch emulation would do anything.
> The q.931 output is definitely more "friendly" with QSIG/NI, as it
> decodes the facility IE.  With 5ESS it doesn't like to receive the  
> name
> id facility ie stuff, it errors on it (but of course call completes).
>
> Brian
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> This message and any attachments are intended only for the use of  
> the addressee and may contain information that is privileged and  
> confidential. If the reader of the message is not the intended  
> recipient or an authorized representative of the intended  
> recipient, you are hereby notified that any dissemination of this  
> communication is strictly prohibited. If you have received this  
> communication in error, please notify us immediately by e-mail and  
> delete the message and any attachments from your system.
>
> _______________________________________________
> 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