To connect to SIP servers other than Sipelia™ Server, you can add a SIP trunk in Config Tool, and then define applicable dial plan rules to make and receive calls between the SIP servers.
What you should know
- SIP trunks work together with dial plans. For example, to connect Sipelia™ Server to another SIP server (SIP Server A) through a SIP trunk, you must define dial plan rules that instruct Sipelia™ Server about which calls to reroute through the trunk and on towards the new SIP extension destinations that are registered to SIP Server A. Furthermore, if you want proper two-way communication between Sipelia™ Server and SIP Server A, both SIP servers need to be configured accordingly.
- When Sipelia™ Server is connected to another SIP server (SIP Server A) through a SIP trunk, SIP Server A can request authentication from the Sipelia™ Server. The Sipelia™ Server must confirm its identity using the credentials configured in .
- When authentication is enabled between trunks, you must ensure that the caller extension is configured as an intercom belonging to another Server. Otherwise, the Sipelia™ Server will revert to its default authentication setting.
Procedure
Results
IMPORTANT: The SIP extension configured for an intercom entity in Security Center is the unique identifier of this
entity. For intercoms connected to an Intercom Exchange Server connected with a
trunk to Sipelia™, this SIP extension must
be used to call the intercom. This extension must also be the identifier used by the
intercom to call Sipelia™ clients. The Dial Plan rules must be properly
configured for these extensions to match.