> Right now, we have a number of different mechanisms that can be used to > do this (the override in sipXbridge that has the 'operator' default, > dial plans, adding aliases to users, etc), but the user has to do them > 'manually'. The administrator should not have to understand the > difference between an alias and a dial plan and a hunt group and an > auto-attendant; they should be able to say "this is an inbound number > and this is where I want it to go" and sipXconfig should choose the > appropriate mechanism.
It would make much more sense to explicitly configure this, as a new user I was confused/surprised that inbound ITSP call mapping was a side effect of not apparently related configuration settings sprayed into various places. Even with that fixed a bigger problem still remains that you're not exactly sure what the ITSP is sending without bouncing servers to enable DEBUG and some fairly painful command line hacking. -Eric _______________________________________________ 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/
