Up to Discussions in OpenSBC
3 Replies Last post: Jun 12, 2007 3:21 AM by kebabber  
Click to view kebabber's profile  
kebabber
2 posts since
Jun 8, 2007

Jun 8, 2007 5:00 AM

Binding OpenSBC to ip on Windows 2003 STD sp2

Hello all :)

I have been running OpenSBC on a couple of Windows servers the last week. Everything works perfect!! So far so good :)

Until today when I installed on a new server. The server has 2 IP addresses on the same interface.

I have tried to bind it in the HTML Admin. Both sip:*:5060 , sip:44.44.44.41:5060 and sip:44.44.44.42:5060. It only binds to "slave" IP rather than the main IP.

My main problem is when a Client connects to this server. Logging in works just fine, for all clients. But when he tries to make a call the "ringing" times out. The other part doesn't get the incoming call.

So anyone have any experience on this field ?

Thanks for a Great software, keep it UP :)
Click to view joegen's profile  
joegen
135 posts since
Apr 28, 2007
1. Jun 8, 2007 6:50 AM in response to: kebabber
Re: Binding OpenSBC to ip on Windows 2003 STD sp2
sip:*:5060 should be enough. OpenSBC has not been tested with virtual IP.  Only multiple NICs with individual IP.
Click to view blackeye1010's profile  
blackeye1010
5 posts since
May 30, 2007
2. Jun 8, 2007 10:04 PM in response to: joegen
Re: Binding OpenSBC to ip on Windows 2003 STD sp2
I think i'm having the same problem on Linux

But if it works with real nics... it should work wit virtual eth's

Any way for the developers to test this ?
I'll be putting up some vmware's to check this out, tomorrow... I'll post my findings then.

Regards
Click to view kebabber's profile  
kebabber
2 posts since
Jun 8, 2007
3. Jun 12, 2007 3:21 AM in response to: joegen
Re: Binding OpenSBC to ip on Windows 2003 STD sp2
I have tried sip:*:5060 .

Its not working with * either, the clients can't make calls.

Might it be a bug or isn't it supported ?

Actions

More Like This