Hi,
I have been experimenting with sipXbridge and I am unable to configure
it to successfully register with bandtel.com
It looks like sipXbridge uses outbound proxy in R-URI of SIP register
requests, while I would expect outbound proxy to be the target of the
SIP requests which should be transparent to the content of the SIP
message.
Bandtel requires R-URI to be bandtel.com while the request should be
sent to proxyx.bandtel.com. With the following configuration sipXbridge
generates a REGISTER request with proxyx.bandtel.com in R-URI.
<itsp-account>
<outbound-proxy>proxyx.bandtel.com</outbound-proxy>
<outbound-transport>UDP</outbound-transport>
<proxy-domain>bandtel.com</proxy-domain>
<user-name>not-telling</user-name>
<password>not-telling</password>
<use-global-addressing>false</use-global-addressing>
<use-rport>false</use-rport>
<register-on-initialization>true</register-on-initialization>
<registration-interval>600</registration-interval>
<use-registration-for-caller-id>true</use-registration-for-caller-id>
<sip-keepalive-method>CR-LF</sip-keepalive-method>
<rtp-keepalive-method>USE-EMPTY-PACKET</rtp-keepalive-method>
</itsp-account>
Register (irrelevant lines omitted):
REGISTER sip:proxyx.bandtel.com SIP/2.0
From: <sip:[EMAIL PROTECTED]>;tag=2791590335185228142
To: <sip:[EMAIL PROTECTED]>
Route: <sip:proxyx.bandtel.com:5060;lr>
Contact: <sip:[EMAIL PROTECTED]:5080;transport=udp>
A well formed request to satisfy bandtel would be sent to
proxyx.bandtel.com and look like the following:
REGISTER sip:bandtel.com SIP/2.0
From: <sip:[EMAIL PROTECTED]>;tag=2791590335185228142
To: <sip:[EMAIL PROTECTED]>
Contact: <sip:[EMAIL PROTECTED]:5080;transport=udp>
Thank you in advance,
Mark.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev