On Wed, Aug 13, 2008 at 6:18 PM, Mark Gertsvolf <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 13, 2008 at 5:51 PM M. Ranganathan wrote:
>> Please use an outbound registrar setting. Bandtel.com needs
>> Registration requests to be sent to registrar.bandtel.com.
>> You can set the registrar address in the advanced settings of
>> the ITSP configuration page.
>
> Hi Ranga,
>
> The instructions that came with my account prescribe the use of
> proxyx.bandtel.com for all requests. I can successfully register and
> make calls using proxyx.bandtel.com as an outbound proxy for both
> registrations and outgoing calls if I use x-lite with a public address.
OK. I can try if you could share your user name and password ( please
send it to [EMAIL PROTECTED] or [EMAIL PROTECTED] ).
>
> I used outbound-registrar setting:
> <outbound-registrar>bandtel.com</outbound-registrar> and the outgoing
> request came out as follows:
>
> REGISTER sip:bandtel.com SIP/2.0
> From: <sip:[EMAIL PROTECTED]>;tag=2791590335185228142
> To: <sip:[EMAIL PROTECTED]>
> Route: <sip:bandtel.com:5060;lr>
> Contact: <sip:[EMAIL PROTECTED]:5080;transport=udp>
>
> This request however still attracts 404 Not found response.
If you can share your account details, I would be glad to experiment
and make sure things are still fine. I had a JIRA issue for
bandtel.com interoperability and it seemed to work. If you wish the
traces for those tests are posted there. Did you download the svn
version recently? I sometimes wonder if our RPMs are getting behind.
>
>
> On a separate note I noticed something else about sipXbridge: It looks
> like sipXbridge was designed for a multihomed machine which has two
> interfaces - one possibly facing the LAN and another facing the WAN.
> I am trying to use sipX on a machine with single NIC card located on a
> private LAN behind a NAT/FW with appropriate port forwarding rules. I am
> noticing that sipXbridge bind to two ports (facing in and facing out)
> and I must set the external-address to be equal to local-address and
> equal to my LAN IP address.
>
> <external-address>192.168.1.4</external-address>
> <external-port>5080</external-port>
> <local-address>192.168.1.4</local-address>
> <local-port>5081</local-port>
>
> sipXbridge uses external-address to bind to SIP port facing out and I
> can't supply my public address in this field as bind fails.
The public address can be specified. You will see something like :
<bridge-configuration>
<external-address>sipxpbx.example.com</external-address>
<global-address>68.33.195.46</global-address>
<global-port>5080</global-port>
......
</bridge-configuration>
You can specify a public (global) address statically ( as above ). You
can also use stun to discover it.
> With that looks like this address is also used in various SIP message
> headers of the requests that are sent out to the public side. I would
> expect global-address to be used instead.
> For instance VIA and Contact headers contain private addresses.
The setting to control this is
<itsp-account>
......
<use-global-addressing>true</use-global-addressing>
---
</itsp-account>
Note that some ITSPs want you to use private addresses and hence the switch.
>
> Does sipXbridge support the above deployment option?
Yes it does.
>
>
> Thank you in advance,
> Mark.
>
Thanks for testing it.
Ranga
--
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
