PVID0 Specifications

As we have already seen it before , if the voice gateway is unable to match an inbound leg for the call , your call will take the properties of the PVID0 .

Don’t forget that you can’t update any properties if the PVID0 is hitted .

Let’s review then the specificities of this default dial-peer:

For POTS dial-peer

  • No IVR applications possible

For VOIP dial-peer

  • Any codec
  • fax-rate voice
  • ip precedence 0
  • No Resource Reservation Protocol ( RSVP)
  • VAD enabled

Outbound Dial Peer leg matching order

As seen with the inbound dial-peer matching , outbound matching is much easier as the dial-peer matches on the destination-pattern expression.
Then the outbound will be selected with the port if you have a POTS dial-peer or will take the session-target in you have a VOIP dial-peer

Inbound Dial Peer leg matching order

When a voice gateway receive a call , you can divide your call in an inbound and outbound leg.

Let’s see how the inbound priority matching .

  1. incoming-called-number (called number “DNIS” information used)
  2. answer-address (calling number “ANI” information used)
  3. destination-pattern (calling number “ANI” information used)
  4. voice-port (that has dial port configured)

How to preserve H323 Calls in a WAN failure

During WAN failure , we can observe that H323 will not preserve absolutely the call when the failover occurs as there is no more any signal from the CUCM.

An unofficial workaround is to use the command h225 timeout to suppress the keepalive between the Call Manager and the gateway.

!

no h225 timeout keepalive

!

Page 17 of 19« First...10...1516171819