[cisco-voip] No Answer duration - 15 Minutes

[Nick Britt]

That did it !

Created new sip profile, increased the invite timer then increased members
no answer duration to 300. The dn's were in a hunt list diverted cfna to
the hunt pilot and it loops for your 15 exactly.

Thanks again chaps!
On 12 Jun 2014 15:23, "Roy Ramos" <irramos at kosmix.com> wrote:

>  For your internal calls the device originating the calls should have a
> sip profile with “Timer Invite Expires (seconds)[image: Required Field]” higher
> than 180 seconds.
>
>
>
> This settings affects this field on your SIP INVITE
>
>
> INVITE sip: @SIP/2.0
>
> Via: SIP/2.0/UDP;branch=z9hG4bKfdd88e6c5c5ddd
>
> From: <sip:>;tag=25120303~a77a1cd4-e106-49f7-8d9b-1ca102a54b6f-108409009
>
> To: <sip:@>
>
> Date: Tue, 17 Dec 2013 21:50:06 GMT
>
> Call-ID: 2f9f0080-2b01c70e-d2dbb9-450213ac@
>
> Supported: timer,resource-priority,replaces
>
> Min-SE:  1800
>
> User-Agent: Cisco-CUCM8.6
>
> Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
> SUBSCRIBE, NOTIFY
>
> CSeq: 101 INVITE
>
> Expires: 180  <------------------------------------
>
>
>  *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On
> Behalf Of *Brian Meade
> *Sent:* Thursday, June 12, 2014 8:55 AM
> *To:* Nick Britt
> *Cc:* Cisco VOIP
> *Subject:* Re: [cisco-voip] No Answer duration - 15 Minutes
>
>
>
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140612/88c2b0bb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 833 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140612/88c2b0bb/attachment.gif>