[cisco-voip] Caller ID changing to inbound dialpeer

[Steve G]

Interesting.  I haven't seen that done before.  But if you have done this
all along, then I don't know if that would be the issue.  Might be worth a
shot though.

On Fri, Nov 20, 2009 at 10:22 AM, Scott Voll <svoll.voip at gmail.com> wrote:

> I have always configured the 911 dial peers as my inbound call leg also.
>  Just saves some dialpeers.
>
> I guess I can remove all the inbound call leg stuff and just create a
> single inbound dial peer.
>
> Scott
>
>
> On Fri, Nov 20, 2009 at 8:38 AM, Steve G <smgustafson at gmail.com> wrote:
>
>> why do you have service ani_filter on an outbound 9911 dial-peer?  why do
>> you have answer-address .... on a 9911 dial-peer?  why do you
>> have direct-inward-dial on an outbound 9911 dial-peer?
>>
>>  On Fri, Nov 20, 2009 at 8:06 AM, Scott Voll <svoll.voip at gmail.com>wrote:
>>
>>>  I just switched from a CMM blade to an ISR VGW.  Setup everything pretty
>>> much the same.
>>>
>>> IOS is 12.4.24t2
>>>
>>> but if a call comes in with OUT caller ID, it looks like it's being
>>> changed to my inbound call leg's destination-pattern (9911).  Nice..... so
>>> everyone is getting calls from 9911 and wondering why the PSAP is calling
>>> them..... with it seems to be a dial-peer issue on my part.  can someone
>>> give me some guidance.
>>>
>>> dial-peer voice 1 pots
>>>  preference 1
>>>  service ani_filter
>>>  answer-address ....
>>>  destination-pattern 9911
>>>  direct-inward-dial
>>>  port 0/0/0:23
>>>  forward-digits 3
>>>
>>> thanks
>>>
>>> Scott
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>>
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091120/6f221740/attachment.html>