[cisco-voip] CallerID H323 IOS 12.4(22)

[David Zhars]

No, no response on getting both name and number.  I am trying a few things,
but no success so far!

Dave

On Thu, Jan 15, 2009 at 2:10 PM, Roush, David <droush at mckennalong.com>wrote:

>  David
>
> Was there ever a response to this with regards to receiving both
> Name/Number? I never saw one on the list serve.
>
>
>
> Thanks.
> David
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *David Zhars
> *Sent:* Wednesday, January 14, 2009 2:54 PM
> *To:* Voice Noob; jbuchanan at ctiusa.com
>
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] CallerID H323 IOS 12.4(22)
>
>
>
> OK, now I get the name but no number!  Is there anyway to have both??
>
> Thanks.
>
>
>  On Wed, Jan 14, 2009 at 2:34 PM, David Zhars <dzhars at gmail.com> wrote:
>
> Yep, it's T.
>
> So I need the 'isdn supp service name-calling'?
>
> I will give that a shot!
>
>
>
> On Wed, Jan 14, 2009 at 11:16 AM, Voice Noob <voicenoob at gmail.com> wrote:
>
> I can confirm that you need .T . I just did this last night, Started with
> mainline and the commands are not there. Switched to .T and works like a
> champ.
>
>
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Scott Voll
> *Sent:* Wednesday, January 14, 2009 9:54 AM
> *To:* David Zhars
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] CallerID H323 IOS 12.4(22)
>
>
>
> David--
>
>
>
> you said 12.4.22...... is this T or not.  My understanding to get it native
> (without TCL script) you have to have a minimum of 12.4.20T.  main line
> would not cover that(at least that is my understanding).
>
>
>
> Scott
>
> On Wed, Jan 14, 2009 at 5:33 AM, David Zhars <dzhars at gmail.com> wrote:
>
> Hi All.
>
> reconfigured my main VGW to H323.  I found a link which says you can now
> get the name and number from CallerID with
> H323, as long as you have version 12.4.
>
> Yet when people call in on the ISDN line, they are just getting the number
> and no name.
>
> Relevant config portion:
>
> voice class h323 1
>   h225 timeout tcp establish 3
>  h225 display-ie ccm-compatible  (this is supposed to be the magic line!)
>
> controller T1 0/1/0
>  pri-group timeslots 9-24
>
> interface Serial0/1/0:23
>  no ip address
>  encapsulation hdlc
>  isdn switch-type primary-ni
>  isdn incoming-voice voice
>  no cdp enable
>
> no ccm-manager fax protocol cisco
> !
> no mgcp package-capability res-package
> no mgcp package-capability fxr-package
> no mgcp timer receive-rtcp
>
> num-exp 8812 1752
>
> Now, the number I am testing with is 555-8812.  Which when it comes in, we
> convert it to 1752 and CCM pushes that to 1712.
> Is it possible with all the number translating and routing I am losing the
> Caller ID name?  Or is this just a pipe dream and the only way
> to get Caller ID Name is with MGCP?
>
> Thanks anyone!
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
>
>
> CONFIDENTIALITY NOTICE:
> This e-mail and any attachments contain information from
> the law firm of McKenna Long & Aldridge LLP, and are
> intended solely for the use of the named recipient or
> recipients. This e-mail may contain privileged
> attorney/client communications or work product. Any
> dissemination of this e-mail by anyone other than an
> intended recipient is strictly prohibited. If you are not a
> named recipient, you are prohibited from any further
> viewing of the e-mail or any attachments or from making any
> use of the e-mail or attachments. If you believe you have
> received this e-mail in error, notify the sender
> immediately and permanently delete the e-mail, any
> attachments, and all copies thereof from any drives or
> storage media and destroy any printouts of the e-mail or
> attachments.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090116/372131f6/attachment.html>