Hello,

We have several projects where we need to handle internal calls but at the moment it is not supported with Breeze.

For example to manage forwardings or redirections based on the caller ID. In bigger companies there are lot of internal calls and we are not able to handle them.
Or managing calls when a service number is called, play announcements and so on.

Is it possible to use an explicit application to handle the internal calls?
How is Explicit Application Sequencing configured in SMGR and Breeze?

Thanks,
Lars

Lars wrote:Hello,

We have several projects where we need to handle internal calls but at the moment it is not supported with Breeze.

For example to manage forwardings or redirections based on the caller ID. In bigger companies there are lot of internal calls and we are not able to handle them.
Or managing calls when a service number is called, play announcements and so on.

Is it possible to use an explicit application to handle the internal calls?
How is Explicit Application Sequencing configured in SMGR and Breeze?

Thanks,
Lars

What mix of phones are you considering? And where are these phones anchored?

The real issue is that if you are talking about H.323 to Digital, H.323 or analog (or any mix of those), you won't ever fling the call over to Session Manager to get in the call flow. A call will stay within CM unless it has to go somewhere else.

If you are talking about SIP -> SIP calls only -- you should be able to execute the call by attaching the application to the user account in the SMGR profile. You should also be able to trigger it via as an implicit application by matching the dialed number.

If you are in a situation where one of the phones are non SIP, and want to get really fancy and potentially break a lot of things, you could modify your uniform dial plan table, mark the station as an AAR number, use the AAR table to send the call to ASM, and execute the application there. Within the ASM, you would then need to manipulate the digits to be sent back to the station in CM and have CM manipulate the digits to make it back to the station. Of course, this will screw up things like voicemail, PPM, AES and a whole slew of other things for that station...

Sorry for my late reply here. Actually, we have problems even with SIP to SIP. Breeze only acts as a B2BUA, not as a proxy. You will encounter problems if you try to put a B2BUA between the endpoint and CM in the sequence vector (before in orig, after in term). Since CM doesn't truly adhere to the "half-call model", you'll run into problems if putting Breeze after CM in orig or before CM in term as well.

The bottom line is that we currently have to stick with our stance that Breeze call intercept snap-ins are only for calls into / out of the enterprise. We are exploring options to expand our supported scenarios, but nothing is committed yet.