Author Message
AndrewProkop
Joined: Oct 27, 2014
Messages: 2
Offline
I have a Call Intercept application that I have loaded, installed, and assigned to a SIP endpoint (via implicit sequencing). If I call from the SIP endpoint to our SIP-based Modular messaging, I see my Snap-in invoked. If I call my cell phone or have my cell phone call the SIP endpoint, it is not invoked. I need some advice as to where to look. Thanks.

Andrew Prokop aprokop@arrows3.com
JoelEzell
Joined: Nov 15, 2013
Messages: 780
Offline
Hi Andrew. Have you come across this white paper? It does a reasonable job of explaining the supported call intercept scenarios. Please read it over (if you haven't already) and let us know if that helps.

http://avayacollateral.netlabs.net/pdfoverview/UC7368.pdf

Andrew.Prokop
Joined: Oct 28, 2014
Messages: 179
Offline
Joel, the documentation is confusing. It states that "calls to or from non-SIP endpoints on Communication Manager over ISDN trunks are not routed through Session Manager" in the section about CM administration. I am using a SIP endpoint as my test phone. Do I still need to run the ISDN trunks through SM? The "non-SIP endpoints" statement tells me that I don't need to change the routing. Do I or don't I? Feel free to call me at 952-456-3516 if you want to discuss this. Thanks.
JoelEzell
Joined: Nov 15, 2013
Messages: 780
Offline
Andrew, I'm sorry that you found the documentation to be confusing. Perhaps we can update it after we conclude this interaction. I'm also sorry that I didn't get a chance to call you today: it's been a very busy day!

The bottom line is that we have tried to normalize behavior between SIP and H.323 endpoints. The statement you quoted was correct: that if you don't have a SIP endpoint or SIP trunk involved in a call, CM will not send the call to SM. Calls to/from SIP endpoints will always traverse SM, but there are subtleties that would complicate the use of Collaboration Environment call intercept snap-ins in ways different than those used by H.323. For instance, Collaboration Environment snap-ins sequenced between a SIP endpoint and CM will break certain CM features. Also, on calls between 2 SIP stations, calling party snap-ins could be invoked after CM has done its termination processing such as call forwarding or setting a voicemail coverage timer.

We are working to rectify these shortcomings so that call intercept snap-ins can be invoked on all calls in the enterprise, but we're not able to do so yet.

If you have any specific suggestions for wording changes in the whitepaper to make this clearer, please let me know and I'll be happy to work on updating it.
Go to:   
Mobile view