| Author |
Message |
dovid
Brekeke Member
Joined: 03 May 2010
Posts: 12
Location: Cyprus,
|
 Posted: Mon May 03, 2010 5:52 am Post subject: Sending 404 when trying to send locally |
 |
|
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/networkpatterns.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. |
|
| Back to top |
|
dovid
Brekeke Member
Joined: 03 May 2010
Posts: 12
Location: Cyprus,
|
| Posted: Wed May 05, 2010 5:44 am Post subject: |
|
|
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. |
|
| Back to top |
|
Harold
Brekeke Master Guru
Joined: 21 Sep 2008
Posts: 289
Location: Japan
|
|
| Back to top |
|
dovid
Brekeke Member
Joined: 03 May 2010
Posts: 12
Location: Cyprus,
|
| Posted: Tue May 11, 2010 5:21 am Post subject: |
|
|
I actually have that set up:
net.net1.interface=66.33.22.101
net.net1.interface-restrict=66.33.22.100 |
|
| Back to top |
|
Harold
Brekeke Master Guru
Joined: 21 Sep 2008
Posts: 289
Location: Japan
|
| Posted: Tue May 11, 2010 11:54 am Post subject: |
|
|
| use net.bind.interface=66.33.22.101 too. |
|
| Back to top |
|
|
