blox

   

francois.collerette

all messages by user

7/11/2018
Topic:
FreeBlox not using the right interface

francois.collerette
francois.collerette
Hi I'm hiting kind of a snag.

Blox is trying to get to my PBX throught the wrong interface. (yeah I know, you think I'm nuts)

So here is my setup for the internal LEG:
PBX (192.168.150.35) -> (192.168.150.1) DMZ Internal (172.31.150.1) -> BLOX (eth1 - 172.31.150.35)

Here is my external leg:
BLOX (eth0 - 10.255.150.35) -> (10.255.150.1) DMZ External -> External IP

When I do a PING, I can reach 192.168.150.35 no problem
When I do a TRACEROUTE, I can reach 192.168.150.35 with 172.31.150.1 without any problem.
So looks like my routing tables are OK

When I look into my DMZ Internal firewall I see this :
DENY 10.255.150.50:47016 -> 192.168.150.35:5060 TCP:SIP
So what is going on ? Why is blox trying to use 10.255.150.50 instead of the 172.31.150.35 ?

I did multiple reboots, checked my routing tables again in SSH and through the FreeBox interface.

I'm clueless at the moment.

Thanks for your help
7/12/2018
Topic:
FreeBlox not using the right interface

francois.collerette
francois.collerette
Hi,

NAT is enabled on EXTERNAL interface.

bloxsupport1 wrote:
Hi Francois,
Have you enabled the NAT setting in Blox? If not please go through the manual/configuration guide to enable the NAT setting.

Regards
Blox Support Team


francois.collerette wrote:
Hi I'm hiting kind of a snag.

Blox is trying to get to my PBX throught the wrong interface. (yeah I know, you think I'm nuts)

So here is my setup for the internal LEG:
PBX (192.168.150.35) -> (192.168.150.1) DMZ Internal (172.31.150.1) -> BLOX (eth1 - 172.31.150.35)

Here is my external leg:
BLOX (eth0 - 10.255.150.35) -> (10.255.150.1) DMZ External -> External IP

When I do a PING, I can reach 192.168.150.35 no problem
When I do a TRACEROUTE, I can reach 192.168.150.35 with 172.31.150.1 without any problem.
So looks like my routing tables are OK

When I look into my DMZ Internal firewall I see this :
DENY 10.255.150.50:47016 -> 192.168.150.35:5060 TCP:SIP
So what is going on ? Why is blox trying to use 10.255.150.50 instead of the 172.31.150.35 ?

I did multiple reboots, checked my routing tables again in SSH and through the FreeBox interface.

I'm clueless at the moment.

Thanks for your help
7/12/2018
Topic:
FreeBlox not using the right interface

francois.collerette
francois.collerette
Hi,

I'm not NAT on the INTERNAL interface.
It's simply routed.

Only the EXTERNAL interface is NATed.

I will try playing with the metrics of the default gateway.
Any clues how I should proceed ?



bloxsupport1 wrote:
By default packets will be routed via external interface for non matching routes.
Blox will bind the port to internal interface (172.31.150.35)
You can try to add explicitly route entry (use metrics) to forward the packets for network 192.168.150.35 and to use the interface.

NOTE: Blox doesn't support Internal side NAT fully, PBX had to be in the same network of internal network or PBX should be enabled to resolve NAT

share us opensips.logs (/var/log/opensips.log) and packet capture on both interface (email: support@blox.org)

francois.collerette wrote:
Hi I'm hiting kind of a snag.

Blox is trying to get to my PBX throught the wrong interface. (yeah I know, you think I'm nuts)

So here is my setup for the internal LEG:
PBX (192.168.150.35) -> (192.168.150.1) DMZ Internal (172.31.150.1) -> BLOX (eth1 - 172.31.150.35)

Here is my external leg:
BLOX (eth0 - 10.255.150.35) -> (10.255.150.1) DMZ External -> External IP

When I do a PING, I can reach 192.168.150.35 no problem
When I do a TRACEROUTE, I can reach 192.168.150.35 with 172.31.150.1 without any problem.
So looks like my routing tables are OK

When I look into my DMZ Internal firewall I see this :
DENY 10.255.150.50:47016 -> 192.168.150.35:5060 TCP:SIP
So what is going on ? Why is blox trying to use 10.255.150.50 instead of the 172.31.150.35 ?

I did multiple reboots, checked my routing tables again in SSH and through the FreeBox interface.

I'm clueless at the moment.

Thanks for your help
7/13/2018
Topic:
FreeBlox not using the right interface

francois.collerette
francois.collerette
I've fixed this.

I went in ifcfg-eth0 and modified :

NM_Enabled=no
METRIC=10

And this did the trick :-)

bloxsupport1 wrote:
Can you share the log /var/log/opensips.log and packet capture to support@blox.org
edited by bloxsupport1 on 7/13/2018
7/13/2018
Topic:
FreeBlox not using the right interface

francois.collerette
francois.collerette
Well seems I didn't.

It works OK in SSH now, but Blox is still trying to use the wrong interface.

Back to the drawing board I suppose.

Any help is appreciated.

francois.collerette wrote:
I've fixed this.

I went in ifcfg-eth0 and modified :

NM_Enabled=no
METRIC=10

And this did the trick :-)

bloxsupport1 wrote:
Can you share the log /var/log/opensips.log and packet capture to support@blox.org
edited by bloxsupport1 on 7/13/2018
8/29/2018
Topic:
Outgoing calls dropped after 30-40 seconds

francois.collerette
francois.collerette
Hi,

my outgoing calls are dropping after 30-40 seconds.

I have check on my PBX side and my PCAP doesn't sow anything out of the ordinary.
I have also checked with my SIP provider and they see nothing out of the ordinary there also.

From what they saw and I noticed also, seems Blox is just sending a "bye" like the call normally "ended".

Please help me sort this.
8/31/2018
Topic:
Outgoing calls dropped after 30-40 seconds

francois.collerette
francois.collerette
Hi,

we are using version 1.0.6.00-24

Here is the output requested :
------------------------------------------------------------------------------------------------------------------------------------------

[root@209 ~]# ps ax | grep blox
1434 pts/0 S+ 0:00 grep blox
1981 ? Ss 0:00 nginx: master process /usr/local/ngx-blox/sbin/nginx
2007 ? S 0:00 /usr/bin/inotify-recursive /var/log/blox-notify
2797 ? S 0:01 /usr/sbin/freeblox -f /etc/freeblox/lighttpd.conf
2800 ? Ss 0:00 /usr/bin/php-cgi -c /etc/php.ini.freeblox
2821 ? S 0:00 /usr/bin/php-cgi -c /etc/php.ini.freeblox
32177 ? Ss 0:00 /usr/local/bin/snort -R eth0 -D -Q -N -k none -q -c /var/etc/blox/etc/dpi.conf
------------------------------------------------------------------------------------------------------------------------------------------


Thanks for your help.

bloxsupport1 wrote:
Hi,
Can you please let us know the Blox version you are using and also output of the below command



Can you also mail us packet capture file from the Blox with your deployment scenario.
Email: support@blox.org

Thanks and Regards
Blox Support Team
8/31/2018
Topic:
Monitoring BLOX

francois.collerette
francois.collerette
Hi,

I'm looking for a way to monitor Blox either through SSH or SNMP.

Thanks for your help.
9/5/2018
Topic:
Outgoing calls dropped after 30-40 seconds

francois.collerette
francois.collerette
Hi also I would like to point out that generally the second time we place a call at the same number, everything works fine.

So let's say I call : 111-222-3365, the call will cut after around 30-40 seconds
If I call back at the same number immediately after, I have no problems.

I will setup PCAP tommorow but I wanted to give you this information since it could help.

bloxsupport1 wrote:
keepalive OPTIONS message sent from Blox for the call live status, which checks for the response for OPTIONS message from both the end of the call.
Can you attach the capture taken on both ends of call (all interface) ?
edited by bloxsupport1 on 9/4/2018

edited by francois.collerette on 9/5/2018
9/6/2018
Topic:
Blox sending Options to Private IP

francois.collerette
francois.collerette
Did you get anywhere with this ?

I'm not having exactly the same issue but looks similar.

Girish wrote:
While on call resulting in sending BYE to either side as OPTIONS is not being responded by Client.
9/6/2018
Topic:
Outgoing calls dropped after 30-40 seconds

francois.collerette
francois.collerette
Here is the capture on both interface ( internal and external)

bloxsupport1 wrote:
keepalive OPTIONS message sent from Blox for the call live status, which checks for the response for OPTIONS message from both the end of the call.
Can you attach the capture taken on both ends of call (all interface) ?
edited by bloxsupport1 on 9/4/2018

edited by francois.collerette on 9/6/2018
11/13/2018
Topic:
Outgoing calls dropped after 30-40 seconds

francois.collerette
francois.collerette
Hi, I know it's been awhile but I'm still experiencing the same problem.

So let's say I call my cell phone ... the call is answered and about 30-40 seconds later the call is cut.
If I call back right away, I have no problem having a long conversation.

I can't wrap my head around this.
Your support is much apprecated.
11/13/2018
Topic:
Outgoing calls dropped after 30-40 seconds

francois.collerette
francois.collerette
I noticed this in the "signaling log"
209 blox-1-0-6-stable[17933]: ERROR:tm:msg_send: tcp_send failed
209 blox-1-0-6-stable[17933]: INFO:dialog:reply_from_caller: terminating dialog ( due to timeout ) with callid = [c6ddce3d-ee24-4fb3-bb05-ce25137b273f]

This is the media log :
209 rtpengine[17564]: Unknown flag encountered: 'force'
209 rtpengine[17564]: [c6ddce3d-ee24-4fb3-bb05-ce25137b273f] Closing call due to timeout
edited by francois.collerette on 11/13/2018
edited by francois.collerette on 11/13/2018
11/14/2018
Topic:
Outgoing calls dropped after 30-40 seconds

francois.collerette
francois.collerette
I am using Skype For Business 2015 which only works in TCP or TLS.
I have this trunk configured in TCP like my other trunks.

The odd things, like I said earlier, is that the second call goes through without any problem.
Almost as if the firstcall "wakes up" the system and then the second call is OK.

bloxsupport1 wrote:
The issue seems to be tcp connection got disconnected for some reason from your phone
Which SIP phone do you use and is it configured with TCP or TLS ?
Can you verify the same with having UDP configured.

francois.collerette wrote:
Hi, I know it's been awhile but I'm still experiencing the same problem.

So let's say I call my cell phone ... the call is answered and about 30-40 seconds later the call is cut.
If I call back right away, I have no problem having a long conversation.

I can't wrap my head around this.
Your support is much apprecated.
1




Powered by blox.org 1.0.0.0 © 2015