[cisco-voip] Inbound calls showing as 911 on IP phones,
H323 gateway
Erick Bergquist
erickbe at yahoo.com
Fri Sep 9 14:12:06 EDT 2005
Ok, Re-entering all the POTS dial peers with different
id's seems to have done the trick for now. The
incoming called-number is first pots dial peer now.
I'm for a bug also, since the example in cisco docs
has the incoming called-number on a higher # dial
peer.
They are 12.3(4)T9 so looking at maybe 12.3(11)T7 ...
I'm working on some other issues with some new bugs in
12.4 so don't want to go there right now. Haven't had
much experience with 12.3(14)T yet so not sure about
that either.
--- "Ortiz, Carlos" <CORTIZ at broward.org> wrote:
> I had this same problem about a year ago. This is
> POSSIBLY an IOS bug.
> Try deleting your dial peers and then re-entering
> them with the one that
> you want to be the incoming call leg first. I
> believe this worked as a
> workaround for me until I either upgraded the IOS or
> switched to MGCP.
>
> Carlos
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On
> Behalf Of Erick Bergquist
> Sent: Friday, September 09, 2005 1:13 PM
> To: Wes Sisk; cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] Inbound calls showing as
> 911 on IP phones,H323
> gateway
>
> I'll try that again, but it wasn't working and I was
> looking at that cisco doc also. Unless I need to
> reboot router to get the dial-peer voice 10 to be
> first since they didn't have one before.
>
> The below is from the doc, which is the case I have
> and it isn't working the way it should work per
> docs.
>
> Special Note on POTS Calls with Empty Calling Number
> Field
>
> Assume this configuration:
>
> dial-peer voice 1 pots
> destination-pattern 9T
> port 1/0:1
>
> Now, assume that an incoming call arrives with no
> calling number information and is matched with the
> POTS dial peer based on the destination-pattern 9T.
> In
> this case, the Cisco IOS router or gateway uses the
> "9" digit as the calling number and forwards the
> call
> to the corresponding device (such as Call Manager or
> the IOS Gateway). In order to not replace the empty
> calling number field, create a dummy POTS dial peer
> with just the command incoming called-number
> configured. Since the incoming called-number
> statement
> has higher priority than destination pattern for
> inbound POTS matching, dial-peer voice 2 becomes the
> POTS dial peer used.
>
> dial-peer voice 1 pots
> destination-pattern 9T
> port 1/0:1
> !
> dial-peer voice 2 pots
> incoming called-number .
>
>
>
> --- Wes Sisk <wsisk at cisco.com> wrote:
>
> > you need a dial-peer appearing earlier in the
> config
> > with the specific port
> > the call is coming in from.
> >
> >
>
http://www.cisco.com/en/US/partner/tech/tk652/tk90/technologies_tech_not
> e091
> > 86a008010fed1.shtml
> >
> > /Wes
> >
> > -----Original Message-----
> > From: cisco-voip-bounces at puck.nether.net
> > [mailto:cisco-voip-bounces at puck.nether.net]On
> Behalf
> > Of Erick Bergquist
> > Sent: Friday, September 09, 2005 12:57 PM
> > To: cisco-voip at puck.nether.net
> > Subject: [cisco-voip] Inbound calls showing as 911
> > on IP phones, H323
> > gateway
> >
> >
> > Whoops, forgot to chnage subject on email I sent
> :(
> > Sorry for any confusion.
> >
> >
> > I'm having an issue with a 1760 with IOS 12.3(4)T9
> > where inbound calls on FXO ports show up on IP
> Phone
> > as calls from 911.
> >
> > The gateway is H323 and the calls hit a dial peer
> > with
> > a destination pattern of 911 on them.
> >
> > I added another dummy dial peer with incoming
> > called-number . and the inbound calls are not
> > hitting this and still hit the other dial peer.
> >
> > I have tried all sorts of dial peer combinations
> > and
> > 2-3 dummy dial peers, I put port #s under the
> dummy
> > peers, etc and still the inbound call wants to
> hit
> > the
> > peer with destination pattern 911 on it. I added
> > answer-address ., and tried .T also. Did this
> with
> > destination-pattern, incoming called-number, etc
> > and
> > no luck.
> >
> > Any ideas? This usually works to solve these
> types
> > of
> > problems and theres a cisco doc that saids to add
> > dummy dial peer with just incoming called-number
> .
> >
> > I also disabled caller-id on the ports and same
> > issue
> > just to rule out caller id.
> >
> > voice-port 3/0
> > input gain -3
> > echo-cancel suppressor 10
> > no vad
> > no comfort-noise
> > timing hookflash-out 50
> > connection plar 4020
> > station-id name Outgoing Laf
> > caller-id enable
> > !
> > voice-port 3/1
> > input gain -3
> > echo-cancel suppressor 10
> > no vad
> > no comfort-noise
> > timing hookflash-out 50
> > connection plar 4020
> > station-id name Outgoing Laf
> > caller-id enable
> >
> > dial-peer voice 9111 pots
> > destination-pattern 911
> > port 3/0
> > forward-digits 3
> > !
> > dial-peer voice 9112 pots
> > preference 1
> > destination-pattern 911
> > port 3/1
> > forward-digits 3
> >
> > dial-peer voice 500 pots
> > answer-address .T
> > destination-pattern .T
> > incoming called-number .T
> > !
> > dial-peer voice 10 pots
> > preference 1
> > incoming called-number .
> >
> >
> >
> > "Many of life's failures are people who
> > did not realize how close they were to
> > success when they gave up."
> > - Thomas A. Edison
> >
> >
> >
> >
> >
>
______________________________________________________
> > Click here to donate to the Hurricane Katrina
> relief
> > effort.
> > http://store.yahoo.com/redcross-donate3/
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> >
> https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
>
>
>
>
>
>
______________________________________________________
> Click here to donate to the Hurricane Katrina relief
> effort.
> http://store.yahoo.com/redcross-donate3/
> _______________________________________________
> 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
More information about the cisco-voip
mailing list