mgoegel Posts: 3
8/18/2017
|
Hello,
i can't make outbound calls due to a not understood(?) URI argument.
Could you help me with that?
Regards Mario
|
|
0
link
|
mgoegel Posts: 3
8/18/2017
|
It's the INVITE request, where a "user=phone" is added. I'm unable to post it here, as the forum every time rejects with an error message, when I try to post it.
Regards Mario
|
|
0
link
|
bloxsupport1 Posts: 232
8/20/2017
|
Can you please let us the know the version of blox you are using and also please send us your deployment scenario ,Please send us the output of the following command, $ rpm -qa | grep blox $ ps ax | grep blox
|
|
0
link
|
mgoegel Posts: 3
8/21/2017
|
Hi,
I downloaded the latest version last week and reinstalled from scratch.
Output is: [root@sbc ~]# 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 blox_rtpengine-1.0.4-8.x86_64 freeblox-1.0.4-8.x86_64 [root@sbc ~]# ps ax | grep blox 1581 ? S 0:39 /usr/sbin/freeblox -f /etc/freeblox/lighttpd.conf 1583 ? Ss 0:00 /usr/bin/php-cgi -c /etc/php.ini.freeblox 12598 ? S 0:02 /usr/bin/php-cgi -c /etc/php.ini.freeblox 15349 ? Ss 0:15 /usr/local/bin/snort -R eth0 -D -Q -N -k none -q -c /var/etc/blox/etc/dpi.conf 62700 pts/3 S+ 0:00 grep blox
I have 1 WAN and 1 LAN interface. I created one WAN SIP profile, a LAN profile and attached them to a SIP trunk.
Inbound calls will be routed to my PBX, so this part is fine. It's just about the outbound calls, which won't be assigned to the SIP trunk domain (I believe), as my PBX sends appends the request URI (and "To" destination URI) with an "user=phone" parameter. It looks like, this will blox not find it's destination domain.
Regards Mario
|
|
0
link
|
bloxsupport1 Posts: 232
8/22/2017
|
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. then download it and send the file to support@blox.org
mgoegel wrote:
Hi,
I downloaded the latest version last week and reinstalled from scratch.
Output is: [root@sbc ~]# 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 blox_rtpengine-1.0.4-8.x86_64 freeblox-1.0.4-8.x86_64 [root@sbc ~]# ps ax | grep blox 1581 ? S 0:39 /usr/sbin/freeblox -f /etc/freeblox/lighttpd.conf 1583 ? Ss 0:00 /usr/bin/php-cgi -c /etc/php.ini.freeblox 12598 ? S 0:02 /usr/bin/php-cgi -c /etc/php.ini.freeblox 15349 ? Ss 0:15 /usr/local/bin/snort -R eth0 -D -Q -N -k none -q -c /var/etc/blox/etc/dpi.conf 62700 pts/3 S+ 0:00 grep blox
I have 1 WAN and 1 LAN interface. I created one WAN SIP profile, a LAN profile and attached them to a SIP trunk.
Inbound calls will be routed to my PBX, so this part is fine. It's just about the outbound calls, which won't be assigned to the SIP trunk domain (I believe), as my PBX sends appends the request URI (and "To" destination URI) with an "user=phone" parameter. It looks like, this will blox not find it's destination domain.
Regards Mario
|
|
0
link
|
hmmartinez Posts: 18
3/14/2018
|
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).
|
|
0
link
|
bloxsupport1 Posts: 232
3/14/2018
|
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).
|
|
0
link
|
hmmartinez Posts: 18
3/15/2018
|
I send you an email with all information.
Also, I send "/var/log/opensips.log" file where appear next Error:
ERROR:core:parse_uri: bad port in uri (error at char : in state 8) parsed: sip:112@172.X.X.X:5060 (25) sip:112@172.X.X.X:5060:5060;transport=udp (44)
Port is duplicated and I don't know why.
Thanks. edited by hmmartinez on 3/15/2018
|
|
0
link
|
hmmartinez Posts: 18
3/15/2018
|
After to upgrade from 1.0.4.8 to 1.0.6.19, problem with "bad port in uri" has disappear.
Thanks & Regards,
|
|
0
link
|
bloxsupport1 Posts: 232
3/15/2018
|
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
|
|
0
link
|