System information

To enable h323-SIP conversion the runsipproxy global config values must be set to true.
Local and LAN IP’s should be also enabled.
These are can be enabled from the Configuration Wizard.
The atarongk application can be controlled from the console port if you type the “gk” command
Two important user entry is created automatically during setup used internally for sip to h323 conversion (and inverse):
 "sip2h323caller" traffic sender
 "sip2h323" sip proxy
Make sue that these are present and enabled.
To setup a h323 caller (incoming traffic), there is no special action to do. You just have to add a traffic sender user with the proper authentication.
For outgoing traffic you must use a "H323 GW/GK" user type and then add it to your routing
In case of H323 entries, the "callsigaddress" field is used instead of the "port" field. This must be set to 1720 usually (standard H323 signaling port). The
media ports are negotiated automatically.
Make sure that atarongk and vsip is enabled on the firewall.
Technical background:
h323 to h323:
1. incoming call arrive to atarongk
2. atarongk will call the routing and will get the destination address
3. atarongk forwards the call to the destination
h323 to sip conversion:
1. incoming call arrive to atarongk (h323 protocol)
2. atarongk will call the routing
3. call will be forwarded to vsip converter
4. vsip will call the routing again (sip protocol)
5. the rest of the call is handled by mizu sipstack
sip to h323 conversion:
1. incoming call arrive to mizu sipstack (sip protocol)
2. call will be sent for vsip
3. vsip will send the call to atarongk (h323 protocol)
4. atarongk will call the routing again
5. atarongk will forward the call to the destination
Troubleshooting: