[cisco-voip] No Answer duration - 15 Minutes

[Nick Britt]

Cheers Matt unfortunately tried that regardless of the forward behavour the
calls still seems to be cutting at 3.

Brian - I will give that a shot and report back





On Thu, Jun 12, 2014 at 2:54 PM, Brian Meade <bmeade90 at vt.edu> wrote:

> Nick,
>
> We might be able to get this working internally but I'm not sure your E1
> carrier is going to let you keep the call in an alerting state for that
> long.  For the external call, where do you see the disconnect coming from?
>
> If you grab CallManager traces for a SIP to SIP call, we can see which
> timer is being triggered to disconnect the call if it's coming from CUCM.
>  Same thing for your MGCP scenario.
>
> Brian
>
>
>
> On Thu, Jun 12, 2014 at 5:14 AM, Nick Britt <nickolasjbritt at gmail.com>
> wrote:
>
>> Morning/Afternoon,
>>
>> We have a need for calls to ring a shared line (unanswered) for up to 15
>> minutes.
>>
>> CUCM 9.1.2 SIP enviroment 8945/9951 endpoints.
>>
>> We are currently are seeing disconnected on internal (SIP to SIP calls)
>> after 3 minutes and 2:30minutes for external calls (E1 > MD110 > MGCP >
>> CUCM).
>>
>> I can see that the unanswered timers on the line can be set to 300
>> seconds (this would be a good start) but as mentioned above the call is
>> disconnected after 3 minutes regardless of this setting.
>>
>> I have tried increasing the SIP INVITE Timers  to more than the default
>> of 18000 milli seconds but to no avail.
>>
>> Is there any other timers that could be modified to resolve this issue?
>>
>> Cheers
>>
>> --
>> - Nick
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>


-- 
- Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140612/4697ec5a/attachment.html>