Version 0.6
26 August 2004
Page 28 of 52
For use with Vega 50 8 FXS + 2 FXO – SIP version 09.02.05.2 T003 or greater.
© 2004 VegaStream Ltd.
8. Configure Registration
FXS:
FXS port registration provides the SIP proxy with two main pieces of information:
•
“address” – the public address of the Vega port (the URL which other SIP endpoints will
use to make calls to this port)
•
“contact” – the URL which the proxy is to use to make the call on that port on the Vega
When a SIP call request is sent to the SIP proxy, it receives the call to a public address, it then
performs a translation from the public address to the contact format, and uses the contact format
to present the call to the Vega.
FXO
Typically trunking ports, like the FXO ports on this unit do not need to register with a SIP proxy.
SIP registration was designed for end users to register themselves with the current local SIP
proxy. Trunking ports potentially support many millions of end users (the whole of the PSTN
network) and so typically the presence and capabilities of the gateways are manually configured
into the SIP proxy.
For telephony to SIP calls, the SIP proxy is usually manually configured to accept calls from the
FXO ports
•
the interface ID on which the call arrived will be in the request URI
•
where supported and enabled the caller ID will be provided in the SIP From: or RPID:
header
For SIP to telephony calls the Proxy must send the call to the Vega 50 FXO with a request URI of
the format
iittt…t@contact_address
•
where
ii
is the interface number through which to make the call (Vega interface 06 to
13), and
•
where
ttt…t
is the telephone number for the Vega to dial
In some circumstances the SIP proxy does demand that the Vega registers with it. If so, configure
registration in the same way FXS registration is configured.
FXS and FXO:
The Registration format is:
--- address:
Public_Address@Registration_Domain
--- contact:
<sip:DN@Host_Name_or_IP_address_of_Vega>
The Vega registers twice for each physical port – once using a numeric address, and once using an
alphanumeric address. Both registrations use the same contact address, so that when a call arrives,
the Vega is not aware of whether the call was made using the numeric URL, or whether the call was
made using the alphanumeric URL.
