[cisco-voip] remote destination question

[Erick Wellnitz]

I've noticed recently that you need to play guessing games for the
different timers based on different cell carrier's settings, whether you
want corporate VM to pick up or the cell VM and tinker with the timers
based on user preference.

I like that flexibility but it can really be a pain sometimes to get all
the timers just right.


On Wed, Jul 10, 2013 at 4:12 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

> We've also found that for SNR clients, we also raise the ring no answer
> duration to 25 seconds on the IP phone to help make the system work better.
>
> Sent from my iPhone
>
> On 2013-07-10, at 5:07 PM, Jason Faraone <JFaraone at paulo.com> wrote:
>
> > The value is in ms and it really depends on your environment. How long
> will it take hotline users to answer the phone before it is forwarded (and
> automatically answered via cell voicemail) to a busy line?
> >
> > I'd guess 5000 would be a safe value to start.
> >
> > I have the opposite problem; my cell phone would only ring once or so
> before the call would hit my corporate voicemail. I had to set the answer
> too late timer to 18000.
> >
> > -----Original Message-----
> > From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf
> Of Kenneth Hayes
> > Sent: Wednesday, July 10, 2013 3:59 PM
> > To: Lelio Fulgenzi
> > Cc: cisco-voip
> > Subject: Re: [cisco-voip] remote destination question
> >
> > What should that timer be set too?
> >
> > Sent from my iPhone
> >
> > On Jul 10, 2013, at 3:58 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> >
> >> There is an 'answer to quickly' timer that you can/should set to avoid
> this.
> >>
> >> Sent from my iPhone
> >>
> >> On 2013-07-10, at 3:53 PM, Erick Wellnitz <ewellnitzvoip at gmail.com>
> wrote:
> >>
> >>> I think this is expected behavior but I would like some input from
> everyone.
> >>>
> >>> We have a hotline number that also has a remote destination
> associated.  When the 'on call' person calls the hotline from their cell,
> it rings once then goes to the voicemail of the cell.
> >>>
> >>> This makes sense because the cell has an active call to the hotline
> and the remote destination initiates a call back to the cell.
> >>>
> >>> I think I could block this by using an access list to not ring the
> destination if it is one of the numbers in the on call rotation that is
> calling.
> >>>
> >>> Does that sound right?
> >>>
> >>> Thanks!
> >>> _______________________________________________
> >>> cisco-voip mailing list
> >>> cisco-voip at puck.nether.net
> >>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>
> >> _______________________________________________
> >> cisco-voip mailing list
> >> cisco-voip at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/cisco-voip
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> 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/20130710/2f47bf71/attachment.html>