On Wed, Mar 3, 2010 at 9:23 AM, Carolyn Beeton <[email protected]> wrote: >> -----Original Message----- >> From: M. Ranganathan [mailto:[email protected]] >> Sent: Wednesday, March 03, 2010 9:20 AM >> To: Beeton, Carolyn AVAYA (CAR:9D60) >> Cc: Mossman, Paul AVAYA (CAR:9D30); [email protected] >> Subject: Re: [sipX-dev] XX-7695 , ITSP templates and settings question >> >> On Wed, Mar 3, 2010 at 9:09 AM, Carolyn Beeton >> <[email protected]> wrote: >> > >> > On the Gateway screen, the Address and Port should be the >> Address and >> > Port of the Gateway. They should not contain the Domain >> and Port of >> > the ITSP at the far end of the Gateway, which is how they are >> > currently being used for a sipXbridge SBC. I think this is >> more than >> > a labelling issue. We can't change Address to Domain because for >> > "normal" Gateways, this is in fact the Address of the >> Gateway, not the >> > Domain of what is beyond the Gateway (which would be >> programmed into the Gateway itself). >> > >> > Unfortunately other than agreeing that the modelling of sipXbridge >> > SBCs is very confusing, I don't have any concrete suggestions for >> > improvement. >> >> >> An address is a domain. Thus if no port is specified, it >> should be treated like a domain. If a port is specified that >> is the listening port of the ITSP. >> >> This is consistent with how SIP does lookups. Yes its not >> very clear but it has not caused confusion to users so I do >> not think we need to fear that it will in the future. >> >> > > An address is a domain, but the gateway address should be the gateway domain. > We are putting the ITSP domain into the gateway domain field.
Any such change we do now will have significant impact for sipxbridge. I request that we leave things the way they are at present. SipXbridge is expecting to see the ITSP domain in the request URI for an incoming INVITE that it needs to forward. Regards, Ranga > > Carolyn > -- 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/
