On Fri, Mar 5, 2010 at 1:30 PM, Nathan Nieblas
<[email protected]>wrote:

> Why hasn't this (multiple matching dial plans with schedules applied) made
> the cut for a release yet? This should be standard functionality and have
> been included with the schedule feature in the dial plan. I just considered
> this a broken function until 4.1 is released...
>
> This is out of the box functionality with Cisco products, mainly exhaust
> all possible matches until there is an exact match (think ACL's).
>
>
> Nathan Nieblas
>
> SACA Technologies, Inc.
> 1260 N. Hancock Street, Suite 102
> Anaheim Hills, CA 92807
>
> p: 714-777-3222 x113
> f:  888-603-9033
> e: [email protected]
>
> -----Original Message-----
> From: [email protected] [mailto:
> [email protected]] On Behalf Of Scott Lawrence
> Sent: Friday, March 05, 2010 9:51 AM
> To: Sven Evensen
> Cc: [email protected]
> Subject: Re: [sipx-users] Is this how dial plan is meant to work?
>
> On Fri, 2010-03-05 at 16:50 +0000, Sven Evensen wrote:
> > I have in Dial Plans one custom dial plan which strips area code etc
> > off incoming numbers,
> >
> > eg 123456 + 4 digits = “matched suffix”. Schedule “always”. Works
> > perfectly.
> >
> >
> >
> > But now I want similar dialplan with an “out of hour” schedule where
> > all calls go to voicemail
> >
> > eg 123456 + 4digits = 8 + “matched suffix”, schedule = “OutOfHours”.
> > This is placed before
> >
> > the previous dial plan.
> >
> >
> >
> > What happens is when “out of hours”, incoming calls go to voicemail.
> > But when the time is outside
> >
> > the schedule (ie in hours), the calls get rejected.
> >
> >
> >
> > I believe this is because sipX finds the first match, sees that
> > schedule does not match and the exits.
> >
> > It should of course continue searching for a match where all criteria
> > are met.
>
> The short answer is that it's doing what the current design calls for it
> to do, and what you're trying to do won't work (clever idea, though!).
>
> The longer answer is that what you tried to do probably should be
> possible.  The reason it doesn't now is that as you discovered, only one
> dial plan is applied at a time.   At present, schedules are implemented
> as an after-the-fact filter, so you never get to the second alternative.
> Fixing this (and some other artifacts with similar causes) is a project
> I'd very much like to take on, but hasn't made the cut for a release
> yet.
>
> > Or is there any other way to accomplish this?
>
> If by "this" you mean not making the caller listen to a few rings before
> going to voicemail after hours, then I don't think so...
>
> You could create a per-user forwarding rule with a schedule just like
> you did in the dial plan - that would work.
>
> You could also try creating a dial plan that matches exactly the number
> of digits in your extensions and puts on the 8 prefix with the
> OutOfHours schedule qualifier, and put it _below_ the other one.
>
> Note however no matter how you do it, after hours _all_ calls would go
> straight to voicemail, even if dialed internally.  Probably not what you
> want - anyone who works late can never get a phone call.
>
>
>
>
> _______________________________________________
> sipx-users mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/
> _______________________________________________
> sipx-users mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/
>


OK, just because Cisco does it doesn't mean everyone should. Though I get
your point, there is a process and procedure for this kind of request. Maybe
because its not in the tracker and/or noone has voted for it to get it
"bumped" up? If there's no files issue how is it supposed to get on "track"?
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to