3/14/2018
Topic:
Outbound call problem with URI
bloxsupport1
|
Hi,
Can you please send us backup configuration of the blox, Goto Tools-->Administration click on the Config backup and also please send us the packet capture.
To take capture, login into the GUI and goto the tools-->Diagnostics-->Packet Capture
Select the Interface as ANY and give the Internal and external ports used, select the timeout for some 90 sec and click on RUN, make an outgoing call, stop the RUN then download it and send the file to support@blox.org.
Can you please send us your deployment scenario/network diagram and also the output the command rpm -qa | grep blox
Thanks
hmmartinez wrote:
Hi, I have the same problem that mgoegel (inbound calls work correctly, but outbound calls don't run and finish call on BLOX (it doesn't make the "nat" from LAN to WAN). |
3/15/2018
Topic:
Unable to upgrade to 1.0.6-19
bloxsupport1
|
Hi,
can you please download and upgrade the latest version of freeblox from "https://www.allo.com/sbc.html" and then you can upgrade the latest blox version 1.0.6-19 from GUI.
Command to upgrade latest version of freeblox
rpm -Uvh [freeblox latest version]
Thanks
hmmartinez wrote:
bloxsupport1 wrote:
Hi,
can you please let us know the file name you are uploading, also send us the output of the command
$ rpm -qa | grep blox".
$ cat /var/tmp/.fw_upgrade.log
$ cat /var/tmp/.firmware_upg
Please send all the details to support@blox.org
Thanks
Hi,
I send us the information:
[root@sip_secure log]# rpm -qa | grep blox
blox_opensips-1.0.4-8.x86_64
blox_ministun_client-1.0.4-8.x86_64
blox_security-1.0.4-8.x86_64
blox-rpm-keys-1.0.4-8.x86_64
blox_rtppinhole-1.0.4-8.x86_64
blox_core-1.0.4-8.x86_64
freeblox-1.0.0-37.x86_64
blox_rtpengine-1.0.4-8.x86_64
About "cat /var/tmp/.fw_upgrade.log" and "cat /var/tmp/.firmware_upg", these files don't exist in my server :-( |
3/15/2018
Topic:
Unable to upgrade to 1.0.6-19
bloxsupport1
|
As your freeblox(GUI) version is out dated so you cannot upgrade the Blox from the present version of freeblox(GUI). To upgrade the Blox you need to upgrade the freeblox to the latest version from the command prompt.
Please follow the below steps to install the Freeblox
Extract the archive freeblox.tar file, using following command
tar xf [download_path]/freeblox.tar
copy the freeblox-x.xx.xx.x86_64.rpm file to the blox machine
Upgrade the freeblox package using the command " rpm -Uvh freeblox-x.xx.xx.x86_64.rpm "
Reboot the system once the installation gets completed
Login to the freeblox GUI using the WAN IP address
Refer the User manual for details regarding accessing theGUI.
Thanks
hmmartinez wrote:
My problem is that I can't upgrade Blox from GUI. System reboot but file version are the same. |
3/15/2018
Topic:
Outbound call problem with URI
bloxsupport1
|
hmmartinez wrote:
After to upgrade from 1.0.4.8 to 1.0.6.19, problem with "bad port in uri" has disappear.
Thanks & Regards,
Thanks for the update  |
3/15/2018
Topic:
FreeBlox character limit on SIP Registrar server
bloxsupport1
|
You need to specify domain:port |
3/22/2018
Topic:
SIP Registration using URL instead of IP Issues
bloxsupport1
|
Hello Noah,
Can you please run the following command and get us the output
$ rpm -qa | grep blox
if you have older version,I suggest you to upgrade to the newer version which is 1.0.6-19
You wanted to do domain routing, you need to add the domain e.g my.url.co.za in the SIP domain (bind port if you use other than 5060)
Then configure roaming user -> inbound route by selecting the domain from dropdown and specify destination domain & uri
You can chk the log file /var/log/opensips.log whether it is processed or dropped due to mismatch with domain
Thanks |
3/22/2018
Topic:
SIP Registration using URL instead of IP Issues
bloxsupport1
|
For the same external SIP profile used in roaming user, you can multiple domain and assign different destination in roaming profile |
3/25/2018
Topic:
SIP Registration using URL instead of IP Issues
bloxsupport1
|
Hi,
You can find the fix/changes available in the below link,
http://forum.blox.org/topic149-version--available-for-download.aspx
For viewing the details of the IP's and other log information you just need to take the move over the particular column, it will display the details.
Thanks and Regard
Blox Support Team.
Noah_SS wrote:
Question about the update, what does it include/change/fix?
A problem I have is viewing the log files on the interface, the columns aren't long enough to view all the details of the IP's etc. |
4/11/2018
Topic:
Fresh Install of Blox + FreeBlox No Interfaces
bloxsupport1
|
Press "Refresh" button in Dashboard page |
4/12/2018
Topic:
Version: 1.0.6 Available For Download
bloxsupport1
|
RELEASE NOTES 1.0.6-24 (Final)
> Fixed NAT issue - oneway voice path
edited by bloxsupport1 on 4/13/2018 |
5/2/2018
Topic:
lost the interface card when install freeblox
bloxsupport1
|
Hi,
Please assign the IP Address manually and access the GUI and Press "Refresh" button in Dashboard page.
Regards
Blox Support Team |
5/15/2018
Topic:
Call Flow on RTP
bloxsupport1
|
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/30/2018
Topic:
Blox GUI FTP down
bloxsupport1
|
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:
IP Block
bloxsupport1
|
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 ISO - Bootable or Broken?
bloxsupport1
|
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. |
6/27/2018
Topic:
SIPS & SRTP
bloxsupport1
|
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 |
7/11/2018
Topic:
FreeBlox not using the right interface
bloxsupport1
|
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
bloxsupport1
|
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
bloxsupport1
|
Can you share the log /var/log/opensips.log and packet capture to support@blox.org
edited by bloxsupport1 on 7/13/2018 |
7/17/2018
Topic:
FreeBlox not using the right interface
bloxsupport1
|
Hi,
Can you please send your deployment scenario with config backup to support@blox.org
Regards
Blox Support Team
francois.collerette wrote:
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 |