On Mon, Feb 22, 2010 at 3:18 PM, Paul Mossman <[email protected]> wrote: > 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? >
On Mon, Feb 22, 2010 at 3:18 PM, Paul Mossman <[email protected]> wrote: > 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? The current GUI implicitly supposes a 1-1 mapping between ITSP and gateway. What we need is a many to one mapping from gateway to ITSP account. Also, you can enter identical ITSP information twice in the GUI in which case you get two records in sipxbridge.xml which are identical except for the line ID. This is unacceptable. Instead what is needed is a single ITSP account with two line ID's both mapped to the same ITSP account. Note too that we can have multiple ITSP accounts with the SAME ITSP domain as well. Thus we need a way of distinguishing between these accounts when making the association between gateway and ITSP account. A simple solution would be to associate a key with the ITSP account and separate the ITSP account configuration from gateway configuration. Or you can have a line ID associated with the gateway and have multiple line ID's associated with the same ITSP account (this is the preferred solution). Regards Ranga > > -Paul > [email protected] > > -- M. Ranganathan _______________________________________________ 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/
