Re: caller id

guckengc · ‎12-20-2000

We are using redundant callmanagers with 2600s as voice gateways and 7960s for phones. Once and while we get inbound calls where the inbound number is passed as 911 or our local area code. This should be coming in as number unavailable. How can we fix this?

jkurth · ‎12-20-2000

I do not think the call manager would be getting the call unless you have an voip dial peer on the gateway which points at the call manager and has a destination of 9T or .T or something to this effect.

Is this the case?

guckengc · ‎12-20-2000

I dont see it....

voice-card 1

!

ip subnet-zero

!

isdn switch-type primary-5ess

isdn voice-call-failure 0

call rsvp-sync

cns event-service server

!

voice class h323 1

h225 timeout tcp establish 10

!

controller T1 1/0

framing esf

linecode b8zs

cablelength long gain36 -22.5db

pri-group timeslots 1-24

!

interface FastEthernet0/0

ip address 172.20.0.5 255.255.0.0

duplex auto

speed 100

h323-gateway voip interface

h323-gateway voip h323-id vgoh

!

interface Serial1/0:23

no ip address

no logging event link-status

isdn switch-type primary-5ess

isdn incoming-voice voice

fair-queue 64 256 0

no cdp enable

!

ip classless

ip route 0.0.0.0 0.0.0.0 172.20.0.1

ip http server

!

voice-port 1/0:23

input gain 5

output attenuation 5

echo-cancel coverage 32

no comfort-noise

timeouts interdigit 3

!

dial-peer cor custom

!

dial-peer voice 911 pots

destination-pattern 911

direct-inward-dial

port 1/0:23

forward-digits all

!

dial-peer voice 41 voip

destination-pattern ....

voice-class h323 1

session target ipv4:172.20.0.2

dtmf-relay h245-alphanumeric

codec g711ulaw

!

dial-peer voice 7 pots

destination-pattern .......

direct-inward-dial

port 1/0:23

!

dial-peer voice 800 pots

destination-pattern 1800.......

direct-inward-dial

port 1/0:23

prefix 1800

!

dial-peer voice 42 voip

preference 1

destination-pattern ....

voice-class h323 1

session target ipv4:172.20.0.3

dtmf-relay h245-alphanumeric

codec g711ulaw

!

dial-peer voice 411 pots

destination-pattern 411

direct-inward-dial

port 1/0:23

forward-digits all

!

dgoodwin · ‎12-26-2000

Yes, the reason you are seeing 911 as the caller ID for some calls is that when the telco does not send you a caller ID for a call for whatever reason, the router uses the destination-pattern of the originating dial-peer which in this case is 911. This can be worked around by putting another dial-peer in the configuration file before this one that has no destination-pattern. The configuration would look like this:

dial-peer voice 1000 pots

direct-inward-dial

port 1/0:23

!

dial-peer voice 911 pots

destination-pattern 911

direct-inward-dial

port 1/0:23

forward-digits all

!

dial-peer voice 41 voip

destination-pattern ....

voice-class h323 1

session target ipv4:172.20.0.2

dtmf-relay h245-alphanumeric

codec g711ulaw

!

dial-peer voice 7 pots

destination-pattern .......

direct-inward-dial

port 1/0:23

!

dial-peer voice 800 pots

destination-pattern 1800.......

direct-inward-dial

port 1/0:23

prefix 1800

!

dial-peer voice 42 voip

preference 1

destination-pattern ....

voice-class h323 1

session target ipv4:172.20.0.3

dtmf-relay h245-alphanumeric

codec g711ulaw

!

dial-peer voice 411 pots

destination-pattern 411

direct-inward-dial

port 1/0:23

forward-digits all

guckengc · ‎12-26-2000

That worked. Thanks!

bgracely · ‎12-27-2000

Another option is using translation-rules, like this:

Define a translation rule which explicilty uses

no calling number if one is not presented in the ISDN Setup. This should take of the problem your seeing below.

Define a translation rule like the following:

translation-rule 5

Rule 1 null null

Apply the rule to a voice port:

voice-port 1:D

translate calling 5

dgoodwin · ‎12-27-2000

I'm not sure this works. I believe that the keywords NULL and ANY only work for the "from" part of the translation-rule. I haven't tried this in the latest bleeding edge IOS versions, but you cannot translate TO NULL.