[cisco-voip] *67 route pattern with calling line set to restricted

[Erick Bergquist]

Yea, the route group/detail and gateway is set to
default and on route pattern is set to restricted, so
the settings on the route pattern should pass through
right? 

--- Wes Sisk <wsisk at cisco.com> wrote:

> it's configurable
> 1.on the route pattern
> 2. where the route gruop is made a member of the
> route list
> 3. on the gateway.
> 
> check all of those.  there is a slim chance the PSTN
> is not honoring the 
> setting.  all you can do to validate that is use
> q931 translator to look 
> at the outbound SETUP from CM.  the privacy bits are
> part of the called 
> party number and q931 translator decodes nicely.
> 
> /Wes
> 
> Erick Bergquist wrote:
> > Have a situation where have a few 9*67.xxxxxxx
> route
> > patterns and the external party mask is unchecked,
> and
> > calling line presentation is set to restricted on
> RP.
> > Route detail is set to default as well as
> gateway/MGCP
> > endpoint. But when calls go out the outside caller
> is
> > seeing the calling party number still. 
> >
> > The gateway is a 6608. Anyone know what to look
> for in
> > the traces to verify the call is going out as
> > restricted? These *67 patterns used to work in
> past
> > I'm being told. 
> >
> > If you prefix *67 on called party number so it
> goes
> > out PRI with *67 the call fails. 
> >
> > thanks
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> > http://mail.yahoo.com 
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> >
> https://puck.nether.net/mailman/listinfo/cisco-voip
> >   
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com