The VCS is able to act as a gateway between
SIP and H.323, translating calls from one
protocol to the other. This is known as
“interworking”.
By default, the VCS will act as a SIP-H.323
gateway but only if at least one of the
endpoints is locally registered.
You can change this setting so that he VCS
will act as SIP-H.323 gateway regardless of
whether the endpoints involved are locally
registered.
You also have the option to disable
interworking completely.

Overview

Configuring Interworking

Interworking options are configured via:

VCS Configuration > Protocols > Interworking

•

You will be taken to the

Interworking

page.

xConfiguration Interworking Mod

•

H.323 <-> SIP interworking mode

Determines whether or not the VCS will act as a gateway between SIP and H.323 calls.

Off

: the VCS will not act as a SIP-H.323 gateway.

RegisteredOnly

: the VCS will act as a SIP-H.323 gateway but only if at least one of the endpoints is

locally registered.

: the VCS will act as SIP-H.323 gateway regardless of whether the endpoints are locally

registered.

We recommend that you leave this
setting as

RegisteredOnly

(where

calls are interworked only if at least

one of the endpoints is locally registered).
Unless your network is correctly configured,
setting it to

(where all calls can be

interworked) may result in unnecessary
interworking, for example where a call between
two H.323 endpoints is made over SIP, or vice
versa.

Save

Click here to save your changes.

Calls for which the VCS is acting as an
SIP to H.323 gateway are traversal
calls. They will therefore require a

traversal call licence.

The VCS cannot act as an IPv4 to IPv6
gateway at the same time as it is acting
as a SIP to H.323 gateway.