| Author |
|
TomB
Intermediate
Joined: April 24 2006
Posts: 3
|
| Posted: April 24 2006 at 11:49am | IP Logged
|
|
|
Interested in using your LanScape Centrex Proxy™ Server.
I am wanting to use the proxy server with a Vxml server that does not have "blind transfer" capability.
The idea would be that after the Vxml phase was completed, a message of where to forward the call would be routed from the Vxml to the Proxy. The Vxml would then hang up, and the Proxy would catch this event and route to next call leg. Or, can the proxy end the Vxml leg and transfer to another call leg?
Thanks.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: April 28 2006 at 5:41pm | IP Logged
|
|
|
Hi Tom,
We are extremely sorry for the delay regarding this support post. It appears one of our new support employees found a way to turn off our automated support notifications we normally get from this forum. Things are now back to normal and we have reprimanded the newbie. :)
We will post an answer to your question immediately this Monday morning. We hope the delay has not impacted you.
Very sorry. Reply as required,
Support
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 01 2006 at 8:27am | IP Logged
|
|
|
Hi Tom,
It seems that if your vxml server could use Record-Route and stay on the call path, then the vxml server could simply forward the original INVITE call request to the Centrex Proxy server and the Centrex Proxy server would process the call as normal (using additional call routing, etc.). If you can configure your vxml server to remain in the signaling chain, then your ideas should work. The vxml server would then eventually be able to also determine who finally answered the call as it was being routed by our server.
However, without further details on what your vxml server can do, we are taking an educated guess.
Repost as needed,
Support
|
| Back to Top |
|
| |
TomB
Intermediate
Joined: April 24 2006
Posts: 3
|
| Posted: May 01 2006 at 6:26pm | IP Logged
|
|
|
Two assumptions:
1. The Vxml server is not listed in the call path and can only do a disconnect on its end.
2. The Vxml server can indicate through an application server that it wants the call to be transferred.
Can this information be passed from the application server to the Centrex Proxy server to catch the disconnect from the Vxml server and reroute the call?
Thanks.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 02 2006 at 7:00am | IP Logged
|
|
|
Hi Tom,
We understand better what you want to do. We have a few questions for you:
You>>>
The Vxml server can indicate through an application server that it wants the call to be transferred.
<<<Support
How exactly does the Vxml server indicate to an application server that it wants the call to be transferred? Is another protocol other than SIP used? What’s the manufaturer or product name of the vxml server?
You>>>
Can this information be passed from the application server to the Centrex Proxy server to catch the disconnect from the Vxml server and reroute the call?
<<<Support
We need more information from you as to how the vxml server communicates with other applications.
One possible way to accomplish your task would be to modify the SIP BYE messages that come from the vxml server when they hit the Centrex proxy. This can be accomplished by using the C++ plug-in dll that comes with the product. You have the ability to alter any SIP message that is received by the proxy using this plug-in DLL.
BYE messages that are received from the xvml server would be altered to include the SIP “Also:” header to allow the user agent that made the call to the vxml server to blind transfer to another location. Now the question to be answered is: How to communicate from the vxml server to the Centrex proxy the transfer destination.
Final question: What are you using the vxml server for?
Repost as needed,
Support
|
| Back to Top |
|
| |
TomB
Intermediate
Joined: April 24 2006
Posts: 3
|
| Posted: May 02 2006 at 7:33am | IP Logged
|
|
|
The Vxml server is by Voxeo. It can do a supervised transfer but not a blind transfer.
The application server is being developed by us -- so we are in control of the message traffic from the Vxml server and on to the Centrex Proxy server. The application server will also determine where to transfer the call.
So, as I understand it, the plug-in dll could be modified to catch the SIP BYE message sent by the Vxml server and then the call could be transfered to a new location based on information provided from our application server. True?
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 02 2006 at 8:21am | IP Logged
|
|
|
Hi Tom,
You>>>
So, as I understand it, the plug-in dll could be modified to catch the SIP BYE message sent by the Vxml server and then the call could be transferred to a new location based on information provided from our application server. True?
<<<Support
Yes. That is correct.
The good thing is that you are developing the application server yourself. So the plug-in DLL (Centrex Proxy) could receive the transfer information directly from your application server by whatever means you see fit.
Support
|
| Back to Top |
|
| |
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> SIP Proxy and Media Proxy - Pre-Sales Technical Support
Topic: Take Back and Transfer
