[cisco-voip] Outgoing Caller ID, My Router, Telco's PRI

[Wes Sisk]

If MGCP gw then CM's parameters make all the difference.  With 
"CallManager" value CM inspects the number and attempts to guess proper 
plan/type.  Some switches accept 1 plan/type for all calls.  Other 
switches require differentiated plan/type per call 
(international/national/...).

If h.323 gateway the config on the gateway controls the values.

/Wes

On Wednesday, August 12, 2009 11:30:03 AM , Jeff Ruttman 
<ruttmanj at carewisc.org> wrote:
> Well I had great success with AT&T looking at this with me, and indeed 
> we have to send ISDN for plan and National Number for type.  We're 
> currently sending "unknown" for type and plan.  Unknown is fine for 
> our other 2 AT&T PRIs, but not the one in question.  Has to do with 
> the switch type said the tech.
>  
> I see in CM 6.1 where to change these on the PRI port on the GW:  
> Calling party IE number type unknown and Calling Numbering Plan.  Can 
> I just change these and restart the GW without any other 
> repercussions?  Right now they're set to "Cisco CallManager" and the 
> help page says basically to leave it alone unless you know about 
> national dialing plans and such--which I don't really.
>  
> So will this change be as simple as changing the drop down and 
> restarting the GW?  And should I also change the Called party IE 
> number type unknown and Called Numbering Plan?
>  
> Thanks
> jeff
>
> ------------------------------------------------------------------------
> *From:* Fuermann, Jason [mailto:JBF005 at shsu.edu]
> *Sent:* Tuesday, August 11, 2009 4:35 PM
> *To:* 'Wes Sisk'
> *Cc:* Jeff Ruttman; cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] Outgoing Caller ID, My Router, Telco's PRI
>
> We were ok sending them "unknown", but 911 didn't work. We have to 
> override with national ISDN
>
>  
>
> *From:* Wes Sisk [mailto:wsisk at cisco.com]
> *Sent:* Tuesday, August 11, 2009 3:16 PM
> *To:* Fuermann, Jason
> *Cc:* 'Jeff Ruttman'; cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Outgoing Caller ID, My Router, Telco's PRI
>
>  
>
> only other CPE variable is the calling party number plan and type.  
> you may try overriding those.
>
> On Tuesday, August 11, 2009 10:53:41 AM , Fuermann, Jason 
> <JBF005 at shsu.edu> <mailto:JBF005 at shsu.edu> wrote:
>
> Definitely an ATT problem if you see it in q391. I know ATT charges us 
> extra to let us present our DID's. On a side note, good luck getting 
> ATT to believe you. We deal with them all the time and it's constantly 
> "you need to check the programming on your side" as if we hadn't 
> already done that and told them.
>
>  
>
> *From:* cisco-voip-bounces at puck.nether.net 
> <mailto:cisco-voip-bounces at puck.nether.net> 
> [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *Jeff Ruttman
> *Sent:* Tuesday, August 11, 2009 9:45 AM
> *To:* cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> *Subject:* [cisco-voip] Outgoing Caller ID, My Router, Telco's PRI
>
>  
>
> Greetings,
>
>  
>
> If, when doing a "debug isdn q391" on my voice router, I see the 
> Calling Party presenting 10 digits to the PRI, then what else on my 
> side of the Caller ID equation might I alter to have those 10 digits 
> show up on the Called Party's phone?
>
>  
>
> As it stands now, the Called Party sees the number assigned to the PRI 
> itself and not the external mask configured on the phone, not the 10 
> digits I see being presented to the PRI via the debug.
>
>  
>
> Other points of interest:
>
>  
>
> We have 2 other PRIs from AT&T, and I see the same 10 digits presented 
> to those 2 other PRIs, and those numbers DO show up on the Called 
> Party's phone.
>
>  
>
> When I send a call out through the problem PRI and call an AT&T cell 
> phone, I DO SEE the proper caller id on the Called Party phone, but I 
> do NOT when I call, say a Sprint phone or a Verizon phone. 
>
>  
>
> AT&T's response to my questions on the problem PRI:
>
> We would pass the T16OX number for caller id. It is up to the customer 
> to program their equipment with the DID number they want to display. I 
> would have him check with his vendor on his programming. I don't know 
> what else to suggest to him.
>
> So anything I can try?  Push back on AT&T?
>
> Thanks, jeff
>
>  
>
> CONFIDENTIALITY NOTICE: The information contained in this email 
> including attachments is intended for the specific delivery to and use 
> by the individual(s) to whom it is addressed, and includes information 
> which should be considered as private and confidential. Any review, 
> retransmission, dissemination, or taking of any action in reliance 
> upon this information by anyone other than the intended recipient is 
> prohibited. If you have received this message in error, please reply 
> to the sender immediately and delete the original message and any copy 
> of it from your computer system. Thank you.
>
>  
> ------------------------------------------------------------------------
>
>
>   
>  
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   
>
>  
>
>  
> CONFIDENTIALITY NOTICE: The information contained in this email 
> including attachments is intended for the specific delivery to and use 
> by the individual(s) to whom it is addressed, and includes information 
> which should be considered as private and confidential. Any review, 
> retransmission, dissemination, or taking of any action in reliance 
> upon this information by anyone other than the intended recipient is 
> prohibited. If you have received this message in error, please reply 
> to the sender immediately and delete the original message and any copy 
> of it from your computer system. Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090812/a826e271/attachment.html>