Admin Guide - VoIP software provider

‣ sipcfg directory and sipunits directory -required for sip to h323 converter (vsip.exe)To enable h323 the hash323 and can_h323 global config values must be set to true.To enable h323-SIP conversion the runsipproxy global config values must be set to true.These are can be enabled from the Configuration Wizard.The atarongk application can be controlled from the console port if you type the “gk” commandTwo important user entry is created automatically during setup used internally for sip to h323 conversion (and inverse):‣ "sip2h323caller" traffic sender‣ "sip2h323" sip proxyMake 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 routingIn case of H323 entries, the "callsigaddress" field is used instead of the "port" field. This must be set to 1720 usually (standard H323 signalingport). The media ports are negotiated automatically.Technical background:h323 to h323:1. incoming call arrive to atarongk2. atarongk will call the routing and will get the destination address3. atarongk forwards the call to the destinationh323 to sip conversion:1. incoming call arrive to atarongk (h323 protocol)2. atarongk will call the routing3. call will be forwarded to vsip converter4. vsip will call the routing again (sip protocol)5. the rest of the call is handled by mizu sipstacksip to h323 conversion:1. incoming call arrive to mizu sipstack (sip protocol)2. call will be sent for vsip3. vsip will send the call to atarongk (h323 protocol)4. atarongk will call the routing again