Difference between revisions of "Intelligent Internal Routing"
From Kolmisoft Wiki
Jump to navigationJump to search
m |
m |
||
| Line 18: | Line 18: | ||
* Device needs to be assigned to DIDs in order to be reachable from Devices on different servers | * Device needs to be assigned to DIDs in order to be reachable from Devices on different servers | ||
** As example in order for Phone1 to call to Phone2, Phone2 should be reachable over DID, not over local Extension! | ** As an example in order for Phone1 to call to Phone2, Phone2 should be reachable over DID, not over local Extension! | ||
* Each Device can be assigned to only one server | * Each Device can be assigned to only one server | ||
** And this Device should Register to or be accessible from correct server | ** And this Device should Register to or be accessible from correct server | ||
Latest revision as of 04:34, 4 September 2013
It is possible to connect unlimited amount of MOR servers into the Cloud.
And MOR is capable of routing calls over all it's servers internally.
In provided example we have only 3 servers in the Cloud but it is enough for demonstration.
MOR can route calls between:
- Devices (over DIDs)
- Trunks (as PBX'es connected to the MOR)
- Providers (which helps to connect to the PSTN)
In provided example all devices (phones), e.g. 1, 1-2, 1-3, 2, 2-1, 2-3, 3, 3-2, 3-3 can talk between each other.
It is important to remember, that:
- Device needs to be assigned to DIDs in order to be reachable from Devices on different servers
- As an example in order for Phone1 to call to Phone2, Phone2 should be reachable over DID, not over local Extension!
- Each Device can be assigned to only one server
- And this Device should Register to or be accessible from correct server
- Each Provider can be assigned to many servers
- Shortest path to use (reach) this Provider will be used by Internal Routing
