Author |
|
hermes Junior
Joined: October 27 2006 Posts: 64
|
Posted: June 16 2008 at 5:14pm | IP Logged
|
|
|
It could be a good feature if Centrex Proxy could define sequential call routing plans via a database. Now if you change a plan, you need to restart the proxy.
Call "forking" would be one more improvement.
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: June 18 2008 at 9:47am | IP Logged
|
|
|
Hi Hermes,
You are exactly correct. Right now the Centrex SIP Proxy supports generic ODBC database access for registrar database and authentication database but not for call routing database. We have made a note of your request.
By the way, what type of application or deployment are you persuing that required dynamic call routing capability? We are curious…..
Call forking is not supported in the SIP proxy. Maybe some day….
Support
|
Back to Top |
|
|
hermes Junior
Joined: October 27 2006 Posts: 64
|
Posted: June 18 2008 at 10:58am | IP Logged
|
|
|
For example, now we have got a 'Sip service' with three phones wich receive incoming calls. When you want to call to this service you have to call to 'sip:test1@test.com'. We have a 'route calling' like this:
test1 -> test1,test2,test3
If we don´t want to stop the service and we need to add one more phone to the platform, we can´t do it.
If your platform has got a lot of Sip phones you´ll need an ACD but if it only has got a few phones... "dynamic call routing" could be a better option.
Don´t you think so?
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: June 19 2008 at 12:19pm | IP Logged
|
|
|
Yes, you are exactly correct and we agree that a dynamic call routing database interface would be better.
|
Back to Top |
|
|