On Mon, Nov 17, 2008 at 8:53 AM, Damian Krzeminski <[EMAIL PROTECTED]> wrote: > M. Ranganathan wrote: >> Hello >> >> There is a port setting in the advanced section of the Trunking >> Gateway configuration page ( right under the account domain). I am not >> sure why its there. I think it belongs in the ITSP configuration >> section along with the outbound proxy as it would be needed when >> REGISTERing with the ITSP. If this is a good suggestion, I can start >> a JIRA issue to request the change. >> > > It's not a good suggestion. The port is needed although rarely changed. It > does not depend on the type of the gateway. It specifies where SIP > signaling is sent: it ends up in the dialing rules. It's only changed when > your gateway or ITSP listen for SIP signalling on a port different from > standanrd (5060). > > Whether or not this port is used in other places (for example when > configuring ITSP account) is a different matter. I am pretty sure that if > you change it sipXconfig will change the appropriate value in ITSP definition. > > There used to be a hidden itsp-account/outbound-proxy-port parameter that > was set based on this value? Any idea what happened to it? Does sipXbridge > still support it? > D.
Yes it does. It still exists in sipxbridge.xml but I took it out of the bridge-sbc.xml file ( as I thought it was not needed). I can put it back and send you a patch. Ranga > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- 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
