Communications Manager 7.3.1.3 (MTE)
I have an inbound route which uses the script. When a call is answered the calling party can not hear the answering party. There is no two way audio.
If I change the routing for this DID to route directly to an extension the audio works just fine.
I set up a feature code to route directly to this hunt list and that also works just fine,
Any idea why using the script directly in the inbound route would have this symptom?
Submitted by rbfletcher on Fri, 08/07/2015
Permalink
Submitted by raven on Thu, 08/13/2015
Permalink
If you want an inbound route
If you want an inbound route to go to a hunt list, just point the route at the hunt list by selecting the hunt list script. Don't point it at a feature code pointed at the hunt list. That will only work from an extension or IVR.
Further clarification: The Feature code I created works when I dial it directly but does not work when the inbound route points to that feature code. i.e.: if I dial "605" from my phone, it rings all the appropriate phones in the hunt list and when answered works normally. If I have an inbound route that uses the "605" feature code the audio symptom manifests.