Ranga wrote: ... > Sorry about the flippancy there. Here is a potentially > constructive approach : > > > > > 1. Define ITSP as an independent thing under bridge > configuration. The creation of ITSP accounts should not be > coupled with the creation of gateways. > > Give each ITSP a key (we can auto generate the key). We must > decouple the ITSP defintiion entirely from the gateway. > > 2. Allow the user to pick that itsp key when he defines a > gateway and routes a call from the gateway to sipxbridge. > Initially we can just present the user with a set of keys + > domain in a pull down menu even just allow him to enter the > right key in a field. Later we can make this GUI more descriptive.
I understand that there's problem with sipxbridge.xml generation. But the UI change being proposed seems to make it harder to configure a SIP Trunk that routes through sipXbridge. Can you help me understand why the current UI doesn't work? -Paul [email protected] _______________________________________________ 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/
