I got a bit lost in this thread.

I think below it says that "to override the port that sipXbridge should sent 
INVITEs to,  you must append ":<port>" to the Gateway 'Address' value"

I don't understand this.  We do not append port to the gateway address, do we?  
Gateway Address becomes <itsp-proxy-domain> in sipxbridge.xml, and the Gateway 
Port becomes <itsp-proxy-listening-port>.  To override the port that sipXbridge 
sends INVITEs to, you (currently) configure the Port on the main Gateway page.

I think both of these fields (the ITSP domain and port) actually belong on the 
ITSP Account page, together with ITSP Server Address which becomes 
<itsp-proxy-address>.  I think the Gateway screen for SIP Trunks should not 
have Gateway Address/Port fields at all - in this case, the gateway is internal 
to sipXecs and we know all about it, and nothing should have to be configured 
for it - what needs to be configured is the ITSP address/port, and its domain 
and optional address/port (and transport) should all be configured in one place 
- on the ITSP Account page, not the Gateway page.

Carolyn

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of M. 
> Ranganathan
> Sent: Wednesday, March 03, 2010 2:28 PM
> To: sipX developers
> Subject: [sipX-dev] Fwd: XX-7695 , ITSP templates and 
> settings question
> 
> Forgot to cc the list.
> 
> 
> ---------- Forwarded message ----------
> From: M. Ranganathan <[email protected]>
> Date: Wed, Mar 3, 2010 at 12:28 PM
> Subject: Re: [sipX-dev] XX-7695 , ITSP templates and settings question
> To: Paul Mossman <[email protected]>
> 
> 
> On Wed, Mar 3, 2010 at 12:07 PM, Paul Mossman 
> <[email protected]> wrote:
> > Ranga wrote:
> > ...
> >> 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.
> >
> > The ITSP template files have a hidden 'itsp-proxy-listening-port'
> > setting.  None have a value defined, but instead have the comment: 
> > "set automatically from SipTrunk.getAddressPort".
> >
> > So to override the port that sipXbridge should sent INTITEs to, you 
> > must append ":<port>" to the Gateway 'Address' value?
> 
> Yes.
> 
> >
> > Even though 'Address' is really the domain?
> 
> 
> A domain can be an address yes.
> 
> 
> 
>  And the override 'ITSP
> > server address' setting is on the ITSP Account screen, and hidden 
> > under Advanced?
> 
> 
> The ITSP server address is the IP address where the ITSP server runs.
> It is incorrect to assume that this is identical to the domain.
> 
> 
> >
> > Do we know of any instances where an admin would actually 
> need to do 
> > this?
> 
> 
> Yes. Consider that we run sipxbridge at port 5080 which is 
> non standard. If you want to hook up two of our own systems 
> to each other via sipxbridge you would need to set the port to 5080.
> 
> All sipxbridge cares about is that when it sees an inbound 
> INVITE from sipx, it should have the domain of the ITSP in 
> the request URI of the INVITE.
> 
> 
> To see why this is necessary, consider that when sipxbridge 
> is used as the default SBC for internet calling there could 
> be no defined ITSP account. In this case I will get an 
> incoming INVITE with no line ID and only the domain of a non 
> existent ITSP. I will create a dummy account for that ITSP 
> and forward the INVITE.
> 
> Let us not change things for now even if it is not consistent 
> with the way other gateways are configured.
> 
> Ranga
> 
> 
> >
> >
> > -Paul
> > [email protected]
> >
> >
> 
> 
> 
> --
> 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/
> 
_______________________________________________
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