On Fri, 2010-02-05 at 10:59 -0600, Eric Varsanyi wrote: > > Having the default go to operator IMO is reasonable, if you didn't > have that default there nothing would work until the user figured out > what the itsp was sending (which requires a deep dive down to the > command line, DEBUG traces, and sipviewer) and that they should be > using aliases on the AA or users to receive calls at all.
I think that what we really need is a simple way to configure that a given number is an inbound number for the system and what should happen with it - whether that number is a trunk number or a DID for some user. 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. This would have the additional benefit that we could at the same time ensure that these inbound numbers are never routed out to the PSTN just to loop back (currently, there are ways that you can set that up that cause that to happen) [1]. [1] http://track.sipfoundry.org/browse/XX-5380 _______________________________________________ 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/
