I have CURRI playing an announcement when a Direct Inward Dialled number is called, and then the call continues to the called party. The ECCP is set on the DN (using CUCM 11.0).
The called party has a Call Forward No Answer set to another extension. Since the extension's DN also has the same ECCP settings, the announcement is played a second time when the call is forwarded.
Is there a way to prevent the announcement from being played when the call is FORWARDED?
-------------------------------------------------------------------------------------------------
The routing request does not indicate how the call "got" to the trigger point (direct dialed, forwarded, etc.). To CURRI, every call request stands as a unique call request, so there is no way to know if it was forwarded or not.
You might have to think of a different <triggerpointtype> to play the announcement, so that the extension to extension forwards don't trigger the same CURRI response. For example, the initial call passes through a translation pattern that doesn't change the called number, it just triggers CURRI (CURRI _can_ see whether it's a TP or an extension that triggered the request). You can still trigger on the DN for other purposes, but by looking at the <triggerpointtype>, you can determine that no announcement should be played.
I will have the initial called number translate on the gateway to a temp number, have a translation pattern on the CUCM pick it up and translate it to the proper number, and trigger CURRI. That should sort it out.
-------------------------------------------------------------------------------------------------
Again, thanks for a most useful piece of software!
Comments
0 comments
Please sign in to leave a comment.