Date: Fri, 29 Mar 2024 06:16:46 +0100 (CET) Message-ID: <1323885251.4117.1711689406771@static.9.57.119.168.clients.your-server.de> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4116_380575693.1711689406768" ------=_Part_4116_380575693.1711689406768 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The SIP Trunks are used for connecting PrivateServer to a local PBX or t= o a SIP VoIP provider. A Trunk can be used both for receiving and placing c= alls in a bidirectional way.
SIP trunks a= re mainly useful to interconnect EVSS ecosystem with other SIP infrastructure, us= ing an end-to-site security model, featured by PrivateWave Enterprise Edition. SIP trunks = have a very limited usefulness for PrivateWave Professional Edition.
Each SIP Trunk can be used to both receive and place calls.
From the PrivateServer version 2.5 you have two main SIP Trunk's categor= ies:
The former ones entail both TLS and SRTP, while the lat= ter none of them: they use just RTP over UDP (thus without TLS). Which one is to be used depends on many factors, ma= jor one is the kind of PBX on the trunk's end. For example Cisco Un= ified Communications Manager are usually connected to PrivateServe= r via Secure Trunk, while SIP providers most often us= e the Unsecure Trunk.
Apart for trunk's categories, you should get acquainted with the Authent= ication Model, that can be:
SIP Trunks using the Registered Authentication Model need an account on = the other end. Then they use the account's credential to authenticate the T= runk when the PrivateServer is started and every communication that passes = over that Trunk is considered authenticated, thus valid by default, and has= the right to be processed and routed.
SIP Trunks with no registration, on the other hand, do not need for an a= ccount to be setup: instead they use IP address to authorize every SIP comm= unication directed to the PrivateServer . This model implies that any new S= IP communication is authenticated against the sender's IP address (meaning = the one belonging to the PBX connected to the PrivateServer ).
The latter model is mostly used enterprise systems, eg with CUCM. The fo= rmer is mostly used with SIP Providers.
There's no way to perform an unauthenticated SIP INVITE on PrivateServer= ! You can have different authentication models but you cannot choose to en= able an unauthenticated SIP Trunk.
No matter what kind of Trunk you're going to configure on PrivateServer = , you would anyway come throughout the SIP Trunk configuration page in orde= r to complete your setup.
in figure 1. New SIP Trun= k form it's shown the tipical generic new sip trunk form.
The fields have the following meanings:
You can reach figure 1. N= ew SIP Trunk form using the CALL ROUTING men= u inside the Configuration. As you can read in figure 2. SIP Trunk section in call routing menu= there are just 2 links inside it:
For creating a new SIP Trunk you go on the SIP Trunks menu voice and then use the New SIP Trunk in the&= nbsp;SIP Trunk List page (see figure 3. The SIP Trunk list.
For each category and authentication models you are going to find a spec= ific manual page describing the correct configuration and the possible para= meters to be used.
4.1 ENCRYPTED SIP Trunks =E2=86=92
= =20