Some customers deploy several miniSIPServer nodes to build their unified VoIP network around the world.
We give a simple document to describe this network and its configuration. There are two important concepts: T-MSS and L-MSS.
L-MSS means “Local miniSIPServer” which are deployed in local branches or offices to service their local SIP phones or gateways.
T-MSS means “Trunk miniSIPServer” which is used to bridge all L-MSS servers.
Please click here to get more details.
Sometime, we may fail to make outgoing calls through SIP trunk if its service provider has some problem, such as no enough resources, and so on. If customers configure several SIP trunks and they are from different service providers, we can configure miniSIPServer to try another SIP trunk to continue outgoing calls.
In the SIP trunk “outgoing call” configuration, please configure a chained SIP trunk described in below figure.
In some VoIP scenarios, we need configure “SIP trunk” to work with VoIP providers or gateways. When processing media streams, we hope (1) local users/phones should process their streams by themselves without MSS, and (2) MSS should help to relay media stream for all outgoing calls to peer SIP servers or gateways.
To fit these requirements, we update MSS V32 to be able to configure “relay media” item in “SIP trunk”. Please refer to following figure for more details.
By the way, MSS can only relay audio streams at this time, so video streams will be lost if you want to MSS to relay streams.