blox

   

recent posts recent posts - RSS

3 days ago
Topic:
FreeBlox not using the right interface

francois.collerette
francois.collerette
Posts: 5
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
3 days ago
Topic:
FreeBlox not using the right interface

francois.collerette
francois.collerette
Posts: 5
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
3 days ago
Topic:
FreeBlox not using the right interface

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

francois.collerette
francois.collerette
Posts: 5
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
4 days ago
Topic:
FreeBlox not using the right interface

francois.collerette
francois.collerette
Posts: 5
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
4 days ago
Topic:
FreeBlox not using the right interface

bloxsupport1
bloxsupport1
Posts: 179
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
4 days ago
Topic:
FreeBlox not using the right interface

bloxsupport1
bloxsupport1
Posts: 179
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
5 days ago
Topic:
FreeBlox not using the right interface

francois.collerette
francois.collerette
Posts: 5
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
19 days ago
Topic:
SIPS & SRTP

bloxsupport1
bloxsupport1
Posts: 179
bloxsupport1
bloxsupport1
Posts: 179
Topic: SIPS & SRTP
Hi,
Can you please let us know your deployment scenario and your PBX information. Do you have SRTP based sip phones?


Regards
Blox Support Team


jcattan wrote:
Hi,

I've a VM Blox SBC for roaming users who arrive to SBC in SIPS to my PBX in SIP
the SIP protocol conversion is ok

but if i want to secure the RTP with SRTP the calls are not converted and fail ... do i need a transcoding card for that ?
thanks for reply
19 days ago
Topic:
SIPS & SRTP

jcattan
jcattan
Posts: 1
jcattan
jcattan
Posts: 1
Topic: SIPS & SRTP
Hi,

I've a VM Blox SBC for roaming users who arrive to SBC in SIPS to my PBX in SIP
the SIP protocol conversion is ok

but if i want to secure the RTP with SRTP the calls are not converted and fail ... do i need a transcoding card for that ?
thanks for reply
5/30/2018
Topic:
Blox ISO - Bootable or Broken?

bloxsupport1
bloxsupport1
Posts: 179
Hi,
It's Bootable, can you please download it once again and try to install.

Regards
Blox Support Team



SP Steve wrote:
Apologies for the stupid question, but is the current image 1.0.6-24 actually bootable. I am trying to boot it in a VMware instance and it is failing.
5/30/2018
Topic:
IP Block

bloxsupport1
bloxsupport1
Posts: 179
bloxsupport1
bloxsupport1
Posts: 179
Topic: IP Block
Hi,
Please create a new Default Access group from GUI, Goto Network-->Default Access

Regards
Blox Support Team

mario.fernandez wrote:
Hello,

How i can to block access to port 5060 to all IPs except our providers ?

Thanks.
5/30/2018
Topic:
Blox GUI FTP down

bloxsupport1
bloxsupport1
Posts: 179
bloxsupport1
bloxsupport1
Posts: 179
Topic: Blox GUI FTP down
Hi,
It's up now, you can go ahead.

Regards
Blox Support Team.

SP Steve wrote:
Just a heads up, the FTP site with the Blox GUI on it is timing out. Any ETA on when it will be back up?
5/30/2018
Topic:
Blox ISO - Bootable or Broken?

SP Steve
SP Steve
Posts: 2
Apologies for the stupid question, but is the current image 1.0.6-24 actually bootable. I am trying to boot it in a VMware instance and it is failing.
5/30/2018
Topic:
Blox GUI FTP down

SP Steve
SP Steve
Posts: 2
SP Steve
SP Steve
Posts: 2
Topic: Blox GUI FTP down
Just a heads up, the FTP site with the Blox GUI on it is timing out. Any ETA on when it will be back up?
5/30/2018
Topic:
IP Block

mario.fernandez
mario.fernandez
Posts: 1
mario.fernandez
mario.fernandez
Posts: 1
Topic: IP Block
Hello,

How i can to block access to port 5060 to all IPs except our providers ?

Thanks.
5/15/2018
Topic:
Call Flow on RTP

bloxsupport1
bloxsupport1
Posts: 179
bloxsupport1
bloxsupport1
Posts: 179
Topic: Call Flow on RTP
Hi Girish,
Please send us the configuration backup and packet capture to support@blox.org, also let us know the Blox version installed.

Regards
Blox support Team


Girish wrote:
Support,

I am facing an issue where lets say

SIP Client registers (Roaming User) on the External IP and then forwarded to the asterisk via the blox Internal IP. (Phone is able to register). I have three phones (1002, 1006 and 1005) registered in the fashion.

When 1005 calls 1006, the INVITE is received on the external port is then sent to asterisk using the Internal port. When asterisk sends the INVITE back to the Internal port of the blox, blox then sends the INVITE back to the External port to the SIP client. All is working fine here, just that
when the INVITE from the Internal is sent to the External port , blox is not proxying the media but sending the Media IP address of the asterisk.
How can we avoid this , what settings should I put.

edited by bloxsupport1 on 5/16/2018
5/15/2018
Topic:
Call Flow on RTP

Girish
Girish
Posts: 20
Girish
Girish
Posts: 20
Topic: Call Flow on RTP
Support,

I am facing an issue where lets say

SIP Client registers (Roaming User) on the External IP and then forwarded to the asterisk via the blox Internal IP. (Phone is able to register). I have three phones (1002, 1006 and 1005) registered in the fashion.

When 1005 calls 1006, the INVITE is received on the external port is then sent to asterisk using the Internal port. When asterisk sends the INVITE back to the Internal port of the blox, blox then sends the INVITE back to the External port to the SIP client. All is working fine here, just that
when the INVITE from the Internal is sent to the External port , blox is not proxying the media but sending the Media IP address of the asterisk.
How can we avoid this , what settings should I put.
5/2/2018
Topic:
lost the interface card when install freeblox

bloxsupport1
bloxsupport1
Posts: 179
Hi,
Please assign the IP Address manually and access the GUI and Press "Refresh" button in Dashboard page.

Regards
Blox Support Team
5/2/2018
Topic:
lost the interface card when install freeblox

shwork
shwork
Posts: 1
i use the VMware ESXI 6.0 install the Blox-1.0.6-24-stable-x86_64.iso. And i go to #setup page go to setup the Ethernet card ip address.
i ping the blox and blox ping to my pc is ok.

after
install freeblox-1.0.6-24.x86_64.rpm. then reboot the system

i try ping the blow , show request timeout . and check the # ifconfig , only have the lo # Loopback 127.0.0.1




Powered by blox.org 1.0.0.0 © 2015