Difference between revisions of "SIP balancer"
From Kolmisoft Wiki
Jump to navigationJump to search
Line 1: | Line 1: | ||
Currently KOLMISOFT offers a SIP balancer | Currently KOLMISOFT offers a SIP balancer solution that can handle: | ||
1. SIP invites from providers to MOR | 1. SIP invites from providers to MOR | ||
2. Incoming DID numbers to MOR | 2. Incoming DID numbers to MOR | ||
The | The balancer has these features | ||
* Handle incoming calls from DIDs, trunks, providers | |||
* Monitoring of Asterisk server capacity - allows to set how many calls a certain Asterisk server can handle | |||
* If one Asterisk server becomes unresponsive or reached call limit, no mor calls are sent to that server | |||
* Option to determine which incoming calls to send to which Asterisk server, or just send calls to servers | |||
depending on their capacity. | |||
Limitations: | |||
* Balancer cannot handle registrations to multiple Asterisk servers, so devices should register to a certain | |||
Asterisk server (provide correct IP to your clients). | |||
[[Image:SIP_balancer.png]] | [[Image:SIP_balancer.png]] |
Revision as of 15:16, 22 November 2011
Currently KOLMISOFT offers a SIP balancer solution that can handle:
1. SIP invites from providers to MOR 2. Incoming DID numbers to MOR
The balancer has these features
- Handle incoming calls from DIDs, trunks, providers
- Monitoring of Asterisk server capacity - allows to set how many calls a certain Asterisk server can handle
- If one Asterisk server becomes unresponsive or reached call limit, no mor calls are sent to that server
- Option to determine which incoming calls to send to which Asterisk server, or just send calls to servers
depending on their capacity.
Limitations:
- Balancer cannot handle registrations to multiple Asterisk servers, so devices should register to a certain
Asterisk server (provide correct IP to your clients).