yeah, i know that =) i guess i just assumed that max wants to be able to distinguish between pbx users--for the purposes of cdr tracking, caller id, inbound call routing, or whatever else. the process i am describing would take a couple of man-hours at most, even for hundreds of users, and you get a granular level of control and monitoring out of it. i think the ROI is ok there =)
if i were in his position, that is what i would do, anyway. but yeah, it is obviously much easier to just have a single user. On Thu, Apr 2, 2009 at 11:43 AM, Scott Lawrence <[email protected]> wrote: > On Thu, 2009-04-02 at 11:17 -0400, milosz wrote: >> i wonder how easy it would be to >> >> (1) pull the list of extensions off your pbx and throw them in an >> excel sheet (or something) >> (2) use this list to generate a bunch of insert statements for the >> users table in sipxconfig >> (3) use same list & sip passwords to generate cli statements for patton > > No - you misunderstand. You only need _one_ user, and it does not need > to match that of the pbx extensions. It is a single identity for the > gateway. > >> > If you can get the gateway between your legacy pbx and sipXecs to >> > authenticate itself (that is, configure a user in sipXecs for the >> > gateway and put those credentials in the gateway) it would be much >> > better. Note that the user you configure does _not_ need to be the same >> > as the identity in the From header for this to work. The From header >> > can be the extension on the other pbx and the user the gateway >> > authenticates as can be something else entirely - sipXecs doesn't care; >> > all it wants is an identity that has the permission required by the dial >> > plan. This is a _much_ better approach than removing the permission. >> > >> > >> > >> > > > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
