8/10/2017
Topic:
ShoreTel Dropping Call After 30-40 seconds
jbrooksga
|
Would you mind sharing some pointers for a ShoreTel setup? I'm really struggling with trunk registration over the wan to the itsp.
Inbound is working.
edited by jbrooksga on 8/10/2017 |
8/11/2017
Topic:
URI error
jbrooksga
|
Why is the URI below adding another 5060? The FreeBlox interface requires me to enter the port in the trunk details, yet it still structures the URI incorrectly.
The log indicates: sip:+18007422348@bkb.pstn.twilio.com:5060:5060,transport=udp which causes a parse error.
edited by jbrooksga on 8/11/2017 |
8/11/2017
Topic:
URI error
jbrooksga
|
Here is more on that:
Aug 11 18:11:35 96 blox-1-0-4-stable[30566]: ERROR:core:parse_uri: bad port in uri (error at char : in state 8) parsed: sip:+18007422348@bkb.pstn.twilio.com:5060>41) /sip:+18007422348@bkb.pstn.twilio.com:5060:5060;transport=udp (60)
Aug 11 18:11:35 96 blox-1-0-4-stable[30566]: ERROR:core:parse_sip_msg_uri: bad uri sip:+18007422348@bkb.pstn.twilio.com:5060:5060;transport=udp
Aug 11 18:11:35 96 blox-1-0-4-stable[30566]: ERROR:enum:enum_query_2: Parsing of R-URI failed |
8/13/2017
Topic:
URI error
jbrooksga
|
I found the cause of this. The UI was requiring a port to be entered for the server address. Edited the table directly in sqlite3 and removed the 5060 port. Resolved the parsing problem. |
8/14/2017
Topic:
URI error
jbrooksga
|
Just updated FREEBlox to the latest this morning. So there was a mismatch. Here is what I have now.
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.4-8.x86_64
blox_rtpengine-1.0.4-8.x86_64 |
8/24/2017
Topic:
ShoreTel Dropping Call After 30-40 seconds
jbrooksga
|
If anyone has a similar issue, with the help of Blox support this is now working correctly. Internal domain should point to the IP/FQDN of your SBC Eth0, External domain should point to your firewall NAT address.
But this still didn't work until Blox Support corrected an error in the code involving the sending of the incorrect URI back the ITSP. Supposedly this will be fixed in a later release. |