On Mon, Feb 22, 2010 at 11:55 AM, M. Ranganathan <[email protected]> wrote:
> On Mon, Feb 22, 2010 at 11:40 AM, Paul Mossman <[email protected]> wrote:
>> Jason wrote:
>>> This would require some changes in the sipxconfig to allow
>>> define ITSP independently and a gateway could refer to them
>>> by selection.
>>>
>>> Could you have a look and comment on it?
>>
>> So we would need a new screen where you define the ITSP Accounts?  And
>> in order to create "SIP trunk"-type Gateways, you need to have at least
>> one ITSP Account?
>
> You do not need an ITSP account necessarily to have a SIP Trunk
> gateway. You would only need one if you are routing the request to
> SIPXBRIDGE.
>
>
>>
>> The reason would be so that multiple Gateways can use the same ITSP
>> Account?  Therefore you would not have to re-enter the ITSP Account
>> credentials for each Gateway?
>
> No that is not the reason why. Re-entry would be a bad thing ideed and
> you will have people complaining but that is not my primary concern.
> The reason  you would want such a screen because otherwise, you wind
> up with multiple identical entries in sipxbridge.xml and that is a
> problem. sipxbridge can sift through the mess of duplicate entries
> thus created in sipxbridge.xml all the information in it. It is bad
> design.
>
>
>>
>>
>> If so, then:
>>
>> 1. What portion of our customer who use SIP Trunks will have multiple
>> Gateways using the same ITSP Account?  (<10%, 10-25%, >25%?)
>
>
>
> I would say < 10% BUT the more important thing is that these are two
> different things. Why are they coupled?
>
>
>>
>> 2. Of those customers, how many Gateways using the same ITSP Account
>> will they have?  (2-6, 6-12, >12?)
>
>
>
> 3.776 %  Really!
>
> (Just kidding)
>
> But really, polling aside, this is a bad design that is confusing,
> causes needless coupling and is wrong. This must be fixed for that
> reason.
>
>
> Regards,
>
> Ranga




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.



This would be easiest to implement IMHO.

Best regards,

Ranga






>
>
> --
> M. Ranganathan
>



-- 
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/

Reply via email to