12-12-2016 09:23 AM - edited 03-17-2019 08:55 AM
Hi everyone,
I am having issues configuring Call Forwards.
Meaning : what I expect is since I don't have currently voice mail enabled, when an external call arrive on say phone 1. I want that the call be forwarded to phone 2 after 5-6 rings (default is about 3 rings which is not enough in my case).
So in the phone 1 configuration I put Forward No Answer External to Destination Phone 2 which works well.
Then I changed the default for "Forward No Answer Time" in order to have my value (24 secs) for all phones instead of just editing the "No Answer Ring Duration" of phone 1 and all phones.
When I received an external call on phone 1, it rings 5-6 times (24 secs) like expected but then it is forwarded to phone 2 that instantly drops the call.
If I keep the configuration for the forwarding but put defaults settings for the "Forward No Answer Time"(12 secs) , phone 1 rings 3 times (12 secs) then phone 2 rings 3 times too. All is working as expected.
So my thinking was that there is somewhere a timeout that drops the call when it reaches 24 seconds. But I've searched in all the settings and Cisco docs and I don't find anything like that. I mean there are values that must be greater that Forward No Answer Time but they all do are greater already even when I put 24 seconds.
Even if my phone 2 is actually a Hunt Pilot, I still have the same issue.
Can somebody tell me what I should check to resolve this issue?
Many thanks in advance
Solved! Go to Solution.
12-13-2016 07:09 AM
Couple of options:
1. Collect debugs at the gateway to determine the disconnect cause.
2. Contact the carrier to see what they see on their end when the call is disconnected.
Brandon
04-27-2017 09:45 AM
Hello everyone,
I resolved this. It was in fact a setting to change in my GUI from my SIPtrunk provider.
By default, it was set to drop calls after 25 seconds.
Thanks,
12-12-2016 12:02 PM
What is the setting for the T301 timer (in Service Parameters)? Default is 180000 msec. It should be greater than the Forward No Answer Timer.
Brandon
12-12-2016 12:06 PM
Brandon,
It is one of the values I was talking about that are already greater than 24 seconds. (As for this one in particular I let the default setting)
Thanks
12-12-2016 12:12 PM
When set to 24 sec, does phone 2 ever ring? Could your carrier have a ring no answer configuration on the line?
12-12-2016 12:17 PM
Yep, phone 2 does ring but just for like 1 ms then it drops the call.
But when it is set to 12 seconds, phone 2 does ring just fine.
I don't think my carrier have a ring no answer conf because I previsouly had an issue with which an unanswered call was ringing for ever even though the caller had hang out.
Don't ask me how I resolve this issue in particularI didn't, it was the guy that set up the system that did and I don't know how (I can ask though)
12-12-2016 12:40 PM
If you set the internal Forward No Answer destination and call the phone internally does the same thing happen?
12-12-2016 02:25 PM
No, in internal it's all good.
12-13-2016 07:09 AM
Couple of options:
1. Collect debugs at the gateway to determine the disconnect cause.
2. Contact the carrier to see what they see on their end when the call is disconnected.
Brandon
10-13-2017 01:44 AM
04-27-2017 09:45 AM
Hello everyone,
I resolved this. It was in fact a setting to change in my GUI from my SIPtrunk provider.
By default, it was set to drop calls after 25 seconds.
Thanks,
04-28-2017 05:15 AM
Hello Santos, Where is this option exactly? are you taking about SIP expire or connect timer under service parameter > Call Manager ?
04-28-2017 07:16 AM
Hi Anthony,
I wasn't talking about some parameter in CUCM.
The timeout was a setting from my SIP Trunk provider (OVH Telecom).
It was indeed a SIP expire at 25 seconds
04-28-2017 08:30 AM
Oh ok, thanks for your information :)
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