...
| No Format |
|---|
dial-peer voice 211 voip
destination-pattern 91........
voice-class codec 200
session protocol sipv2
session target ipv4:5.6.7.8
|
H.323
...
dial
...
peer
...
that
...
uses
...
RAS
...
(configured
...
gatekeeper).
| No Format |
|---|
dial-peer voice 1 voip |
...
destination-pattern 10......... |
...
voice-class codec 200 |
...
session target ras |
| No Format |
|---|
H.323
...
dial
...
peer
...
that
...
routes
...
to
...
another
...
gw
...
or
...
endpoint
| No Format |
|---|
dial-peer voice 1 voip |
...
destination-pattern 11......... |
...
voice-class codec 200 |
...
voice-class h323 500 |
...
session target ipv4:9.8.7.6 |
...
Specific
...
h323
...
class
...
is
...
configured
...
to
...
change
...
some
...
parameters.
...
SIP
...
UA
...
settings
| No Format |
|---|
* sip-ua |
...
nat symmetric role passive |
...
nat symmetric check-media-src |
...
sip-server dns:domain.dom |
...
Here
...
is
...
defined
...
sip
...
server
...
(used
...
in
...
dial
...
peers)
...
and
...
various
...
sip
...
parameters.
...
Gatekeeper settings
| No Format |
|---|
interterface Loopback0 |
...
description MGMT Loopback |
...
ip address 1.2.3.4 255.255.255.255 |
...
h323-gateway voip interface |
...
h323-gateway voip id GK1 ipaddr 1.1.1.1 1718 priority 100 |
...
h323-gateway voip id GK2 ipaddr 1.1.1.2 1718 |
...
h323-gateway voip h323-id IP2IPGW |
...
h323-gateway voip tech-prefix 1# |
...
h323-gateway voip bind srcaddr 1.2.3.4 |
| No Format |
|---|
Gatekeeper settings for ras session target in dial peers with primary and secondary gatekeeper. It is not necessary to configure it on Loopback interface.
There seems to be a BUG that affects H.323 slowstart to SIP calls if sip server is not set by ipv4:1.2.3.4.
OS specific help
N/A - There is only CISCO IOS
Validation, confirmation tests
Route call through IP2IP gw.
If you don't use sip server and gatekeeper, set dial peer destinations (session-target) directly to endpoints and call each other ( i.e. sip:numberofh323endpoint@ipofip2ip)