Sending 404 when trying to send locally

Discuss any topic about Brekeke SIP Server.

Moderator: Brekeke Support Team

Post Reply
dovid
Posts: 12
Joined: Mon May 03, 2010 5:44 am
Location: Cyprus,

Sending 404 when trying to send locally

Post by dovid »

1. Brekeke Product Name and version: SiP Server V: 2.2.7.8

2. Java version: Not sure

3. OS type and the version: Ubuntu

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

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html : None of those

Server has two IP's (not the real IP's ;) )
66.33.22.100
66.33.22.101

Brekeke is listening on 66.33.22.101. Call weaver is listening on 66.33.22.100. When the call comes in to the Brekeke Sip Server when doing a trace it shows a 404 error.

CallFlow -> ISP -> Brekeke (66.33.22.101) -> To Callweaver (on same box 66.33.22.100).

If in Brekeke I send the call to 66.33.22.101:5065 then it works. It seems that the brekeke is getting confused with the second IP when it should not.
dovid
Posts: 12
Joined: Mon May 03, 2010 5:44 am
Location: Cyprus,

Post by dovid »

I work around was to install OpenSipS listening on 5065 send it there and from the OpenSipS to send it to my CallWeaver.

Over all it seems like a bug in the Brekeke software.
Harold
Posts: 289
Joined: Sun Sep 21, 2008 10:31 pm
Location: Japan

Post by Harold »

It seems you didn't configure the brekeke correctly..

Use "net.bind.interface" setting.
http://www.google.com/search?q=%22net.b ... ke-sip.com
dovid
Posts: 12
Joined: Mon May 03, 2010 5:44 am
Location: Cyprus,

Post by dovid »

I actually have that set up:

net.net1.interface=66.33.22.101
net.net1.interface-restrict=66.33.22.100
Harold
Posts: 289
Joined: Sun Sep 21, 2008 10:31 pm
Location: Japan

Post by Harold »

use net.bind.interface=66.33.22.101 too.
Post Reply