On Tue, 2010-02-02 at 10:14 -0600, Brian Young wrote:
> I know that Sipx does not permit phone based forwarding. 
> 
> Would it be possible to allow this: User picks up the line they want to
> forward, and dial *72 and sipx would take that in a dial plan, and accept
> the digits and then write a forwarding rule erasing all existing forwarding
> rules, if any?  That forwarding rule would be viewable in the GUI. The user
> could then dial *73 to cancel all forwarding.
> 
> I am not asking that these be implemented per se, I am wanting to know if it
> would be acceptable.  If it is, I am going to attempt to implement it
> myself.

Leaving aside any questions of whether or not a prefix code is the right
way to go about it, I see nothing wrong with the general concept of
allowing the user (if properly authenticated) to modify forwarding rules
using DTMF inputs.

A very minor terminology point - we use the term 'dial plan' to refer to
a global routing rule, not to forwarding for individual users.  The two
are implemented by different mechanisms.

I think that the way to do this would be to create an IVR application
that the user could call to make forwarding changes.  The application
would prompt the caller to enter a valid user PIN, and possibly a user
extension (if you call from your own number, you don't get challenged
for the extension).  It could then give the user the opportunity to
insert or delete forwarding entries.  You'd have to work out rules and
user interfaces for how this relates to entries made through the web UI
- if I have forwarding set on my phone to go to my cell, then my
assistant, then my voicemail, it's handy for me to add an entry for the
hotel room I'm in because my cell doesn't work there, but I probably
don't want to delete the forwarding to my assistant or my voicemail.

When that application has a set of changes to be made to forwarding, the
right way to fit it into the rest of the system would be to send the
changes to the sipXconfig management application so that they could be
added to the database (the source of all knowledge and the one thing
that gets backed up) and properly sent to everything that needed to
know.




_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to