XV0500 Video MCU User's Guide
Page 7 of 30
Xorcom Ltd.
● P.O. Box 60, Misgav Industrial Park 20174 ● Tel: +972 4 995-1999 ●
www.xorcom.com
The IP-PBX users will have to dial 52 and then any three digits in order to make a call via the “ConfBridge” SIP
trunk. The '52' prefix will be stripped off automatically from the called number. For example, in order to call
the MCU access number 500, the IP-PBX users would dial 52500.
The SIP trunk approach has the following limitation: the callers who access the IP-PBX via the other trunks
will not be able to call MCU unless either:
a)
“context=from-internal” is defined for those trunks, which significantly decreases the PBX protection
level, or
b)
some special customization for the standard FreePBX dialing plan is implemented.
Alternatively, it is possible to configure the XV0500 to register the access number(s) and/or the conference
number(s) as regular IP-PBX extensions. In this case the external IP-PBX users will be able to call the
conference bridge, just like they would any other IP-PBX extension.
PBX Users Call the MCU Just Like Regular IP-PBX SIP Extensions
a)
Define a SIP IP-PBX extension for each access number and a conference number the XV0500 should
register.
b)
Enable the corresponding access number and/or conference number registration in the XV0500
configuration. (Ref. topic “
Access Numbers
” and “
Conference Management
”.)
Users Call the XV0500 Video MCU Directly
The MCU-CS has its own built-in registrar/proxy SIP server that is by default bound to port 5060/udp.
Optionally it is possible to make inbound SIP calls to the MCU-CS without authentication. This service is by
default bound to port 5095/udp. Those two services allow calling the MCU-CS directly, bypassing the IP-PBX.
Following is an example of an unauthenticated call using Linphone:
