12-04-2013 03:41 AM - edited 03-16-2019 08:42 PM
I setup a call handler that transfers to user extensions fine. If the caller enters an extension number after the greeting they get transferred to the number, but if they hang up before the call is answered the recipient phone continues to ring. I am using cucm and cu 6.
Solved! Go to Solution.
12-04-2013 04:34 AM
Hi anand , I think I replied after you've posted the PSTN setup. I agree with Jonathan , It seems to be a FXO disconnection issue for incoming PSTN calls . Check also the scenario of putting the Cisco Unity Connection in the Picture of call routing and out of it .
12-04-2013 04:36 AM
Hi Anand
Do you use full consultation or release to switch on the CUC ? Try both options
12-04-2013 04:12 AM
this is only for incoming pstn calls
12-04-2013 04:26 AM
pstn -----------> fx0 voice router fa0 -------------> Cucm/cu server
|
fxs
it does not matter if the recipient is an ip phone on cucm, or analog phone on fxs port on the router. the phone contiues to ring after pstn caller hangs up.
fx0 port on router is configured as:
voice port 2/0/0
connection plar opx 1600 (where 1600 is my AA number)
12-04-2013 04:29 AM
This is, to some extent, a limitation of the FXO interface. Here is a document that explains your problem (Scenario 1) and how to address it:
http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a00800ae2d1.shtml
Please remember to rate helpful responses and identify helpful or correct answers.
12-04-2013 04:28 AM
What is the Voice Gateway interface type Analogue or Digital setup ? Does it drops only when the incoming call hits the Unity Connection or for example any incoming to IP Phone
12-04-2013 04:31 AM
yes the call sucessfully drops if it goes to an ip phone or fxs phone directly from pstn. however once i configure calls to go to the AA number instead, the situation i described occurs. see the above diagram in my prev reply for the setup.
12-04-2013 04:34 AM
jonathan i've read that article. I did have the problem before, but entering opx in the connection plar statement fixed that issue.
But now that i have incoming calls going to AA, the issue has occurred again.
12-04-2013 04:41 AM
Hm, that's strange that it would behave differently when routing through CXN. I suggest debuging the router to see whether it believes the port has gone on-hook or not. If it doesn't (and thus doesn't tell CUCM of that fact) then it's not CXN's fault and you're still being impacted by the answer supervision issue I referenced above.
debug vpm signal
debug voip ccapi inout
Please remember to rate helpful responses and identify helpful or correct answers.
12-04-2013 04:34 AM
Hi anand , I think I replied after you've posted the PSTN setup. I agree with Jonathan , It seems to be a FXO disconnection issue for incoming PSTN calls . Check also the scenario of putting the Cisco Unity Connection in the Picture of call routing and out of it .
12-04-2013 04:36 AM
Hi Anand
Do you use full consultation or release to switch on the CUC ? Try both options
12-04-2013 04:39 AM
sorry i pressed correct answer by mistake. how do i uncorrect ?
what's the difference in those 2 options abdel ?
12-04-2013 04:42 AM
Hi Anand
It is simply will instruct the Unity Connection whether to be in the Call path of the incoming calls for further treatment if No-Answer occured OR whether it divert or release the Connection to the CUCM.
12-04-2013 04:44 AM
ok i will try that. where is the setting at ?
12-04-2013 06:56 AM
Hi anand
It is in the Transfer Rule in the System Call handler window . Also Jonathan suggestion is valid as we need to look at the GW level traces as well .
12-04-2013 08:42 AM
the release to switch option is only available if i select a specific extension to be transferred to. This would cause my call handler to transfer any calls to it to this extension, which is not what i would want.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide