Posts Tagged ‘Gateway’

The determining factor for whether a gateway registers with a TYPE of VOIP-GW or H323-GW relies entirely on the “allow-connections” commands entered under “voice service voip.” Essentially, if your gateway is functioning as an IP-to-IP gateway, it will display H323-GW.

The commands that make or break this:

voice service voip
allow-connections h t h
allow-connections h t s
allow-connections s t h
allow-connections s t s

After adding or removing these, make sure to bounce your gateway registration with the gatekeeper using “no gateway” and “gateway.”

I just verified this. Here is a snapshot without the commands listed above:

HQ-RTR#show gatekeeper endpoints
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
————— —– ————— —– ——— —- —–
10.10.202.1 1720 10.10.202.1 58978 Spain VOIP-GW
H323-ID: BR2-RTR
Voice Capacity Max.= Avail.= Current.= 0

After adding the commands listed above:

HQ-RTR#show gatekeeper endpoints
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
————— —– ————— —– ——— —- —–
10.10.202.1 1720 10.10.202.1 50555 Spain H323-GW
H323-ID: BR2-RTR
Voice Capacity Max.= Avail.= Current.= 0

$ means ”end of digits” and is used for a more specific match. If you have two dial-peers with the same pattern and one with $ and the other without $, then call routing logic will always match the one with $, because that is more specific. Even if you give a lower preference to the dial-peer with $, still it will be matched because by default the dial-plan hunting algorithm is more specific match first and then preference.

dial-peer voice 10 pots

destination-pattern 1000

port 1/0/0

dial-peer voice 11 pots

destination-pattern 1000$

port 1/0/0

preference 5

 

In this case, always dial-peer 11 will be used to route calls to 1000, even though it has a lower preference.