BSS with 2 NICs causing mixed use of IPs bug?

wayne106 · Post by **wayne106** » Mon Apr 28, 2008 3:28 am

1. Brekeke Product Name and version: BSS Standard 2.1.6.6

2. Java version: 1.5.0.06

3. OS type and the version: Win2k3 web edition

4. UA (phone), gateway or other hardware/software involved: Any

6. Your problem:

moving my BSS setup over to its live environment, and have come up with a problem, I have 2 NICS in the server, 1 is the public IP 212.x.x.x and the other a private internal IP 100.x.x.x the private IP is connected to the SQL server so that SQL requests don't end up on the 'net.

The problem is that even though SIP requests are coming in on the 212.x.x.x int, BSS is replying using the 100.x.x.x address in the headers but sending them via the 212.x.x.x interface.

I have auto discovery turned off and set the interface address 1 to 212.x.x.x address. In desperation I have even set the External IP address pattern to the 212.x.x.x IP but still BSS uses the 100.x.x.x address. (rebooted server in between changes just in case)

anyone know what I can do? I was looking in SV.properties for the auto discovery on/off entry but cannot find it, does anyone know what it is? I wonder if the GUI is not setting it and its stuck on auto meaning BSS will try and auto use all IP's?

Here a trace of an endpoint connecting:- (the 10.0.0.199 is my voip phone behind my NAT)

Received from udp:212.x.x.x:5060 at 28/4/2008 11:23:41:230 (332 bytes):

OPTIONS sip:username@10.0.0.199:5060 SIP/2.0
Via: SIP/2.0/UDP 100.x.x.x:5060;rport;branch=z9hG4bK26f6467bef
CSeq: 5 OPTIONS
From: sip:100.x.x.x:5060;tag=b3ca849d3s
To: <sip:username@10.0.0.199:5060>
Call-ID: b5312357-4c1a3752-833e0f25-6276763c@100.x.x.x
Max-Forwards: 70
Content-Length: 0

--------------------------------------------------------------------------------

Sent to udp:100.x.x.x:5060 at 28/4/2008 11:23:41:240 (575 bytes):

SIP/2.0 200 OK
Via: SIP/2.0/UDP 100.x.x.x:5060;rport=5060;branch=z9hG4bK26f6467bef
From: sip:100.x.x.x:5060;tag=b3ca849d3s
To: <sip:username@10.0.0.199:5060>
Call-ID: b5312357-4c1a3752-833e0f25-6276763c@100.x.x.x
CSeq: 5 OPTIONS
Contact: <sip:username@10.0.0.199:5060;line=gsf9gv9b>
User-Agent: snom190-3.44
Accept-Language: en
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
Allow-Events: talk, hold, refer
Supported: timer, 100rel, replaces
Content-Length: 0

--------------------------------------------------------------------------------

Sent to udp:212.x.x.x:5060 at 28/4/2008 11:23:42:750 (936 bytes):

INVITE sip:1571@212.x.x.x;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.0.0.199:5060;branch=z9hG4bK-m78wtx6qco8z;rport
From: "wayne106" <sip:username@212.x.x.x>;tag=s9xvt2scnh
To: <sip:1571@212.x.x.x;user=phone>
Call-ID: 3c2a215eb4aa-yymnp2vp1ow0@10-0-0-199
CSeq: 1 INVITE
Max-Forwards: 70
Contact: <sip:username@10.0.0.199:5060;line=gsf9gv9b>
P-Key-Flags: keys="3"
User-Agent: snom190-3.44
Accept-Language: en
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
Allow-Events: talk, hold, refer
Supported: timer, 100rel, replaces
Session-Expires: 3600
Content-Type: application/sdp
Content-Length: 230

v=0
o=root 1337297069 1337297069 IN IP4 10.0.0.199
s=call
c=IN IP4 10.0.0.199
t=0 0
m=audio 10016 RTP/AVP 18 0 101
a=rtpmap:18 g729/8000
a=rtpmap:0 pcmu/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

--------------------------------------------------------------------------------

Sent to udp:212.x.x.x:5060 at 28/4/2008 11:23:42:770 (482 bytes):

SUBSCRIBE sip:1571@212.x.x.x;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.0.0.199:5060;branch=z9hG4bK-b0pia26il2zq;rport
From: <sip:username@212.x.x.x>;tag=6cpeocxbf4
To: <sip:1571@212.x.x.x;user=phone>
Call-ID: 3c2a215eb98c-bhlq6mym66ff@10-0-0-199
CSeq: 1 SUBSCRIBE
Max-Forwards: 70
Contact: <sip:username@10.0.0.199:5060;line=gsf9gv9b>
Event: dialog;purpose=call-completion
Accept: application/dialog-info+xml
Expires: 3600
Content-Length: 0

voipwell.com · Post by **voipwell.com** » Mon Apr 28, 2008 10:49 pm

Hi,

Yes, this is common. You need to restrict the sip server from using the local ip and bind the sip server to the wan ip. Search the forum for restrict and bind and you will see the correct syntax to put into the properties file.

wayne106 · Post by **wayne106** » Tue Apr 29, 2008 1:53 am

Thanks for that, I did have a good look around but I might have missed the archives, the word I should have been looking for was bind!

Solution is this anyway in case anyone else has this problem:-
in sv.properties

net.bind.interface=212.x.x.x
net.net1.interface-restrict=100.x.x.x

restart whole machine (BSS hung after I restarted with new config, but hard restart fixed it)

Wayne