Ryushin Posts: 5
5/10/2017
|
I think I've successfully set up Blox between my ShoreTel PBX and Flowroute.
So my config looks like this: ShoreTel 172.28.202.98 ---> 172.28.202.36(Internal)(Blox)(external)172.28.202.35 --> Fortigate Firewall to Flowroute (using a VIP)
But for some reason I think the ShoreTel PBX is dropping the call after 30-40 seconds probably because it's not receiving something its looking for.
So I'm not quite sure how to proceed at this point.
My Blox logs: http://ix.io/tk8 edited by Ryushin on 5/10/2017
|
|
0
link
|
bloxsupport1 Posts: 232
5/10/2017
|
Can you please send us the packet capture to support@blox.org ?
|
|
0
link
|
mkeys Posts: 6
5/11/2017
|
Ryushin wrote:
I think I've successfully set up Blox between my ShoreTel PBX and Flowroute.
So my config looks like this: ShoreTel 172.28.202.98 ---> 172.28.202.36(Internal)(Blox)(external)172.28.202.35 --> Fortigate Firewall to Flowroute (using a VIP)
But for some reason I think the ShoreTel PBX is dropping the call after 30-40 seconds probably because it's not receiving something its looking for.
So I'm not quite sure how to proceed at this point.
My Blox logs: http://ix.io/tk8 edited by Ryushin on 5/10/2017
Check the signaling logs for the call id (031b3b74-66aaeb22-de3b96) on your shoretel. 30 second timeout sounds like no receipt of the ACK to the 200 OK with SDP. My guess is the contact for the ACK should probably point to the internal interface, but it's going to external or vice versa.
Regards, Matt
|
|
0
link
|
Ryushin Posts: 5
5/11/2017
|
I've changed the network to separate out the networks. It now looks like: ShoreTel 172.28.202.98 --> 172.28.202.35(Internal)(Blox)(external)172.28.90.35 --> Fortigate Firewall to Flowroute (using a VIP)
Same problem just occurred. I feel like I'm cursed.
I'm going to log another packet capture and send it to support@blox.org.
|
|
0
link
|
Ryushin Posts: 5
5/11/2017
|
Looks like I finally got this sorted out, though I will probably have to test further. So the Blox SBC looks like it will work with ShoreTel and Flowroute. My issue was the SIP Domain configuration in Blox. I had the Internal SIP domain using the internal IP address of the Blox SBC instead of using the IP address of the ShoreTel switch. Creating a new SIP Domain with the ShoreTel switch IP fixed the problem.
|
|
0
link
|
jbrooksga Posts: 6
8/10/2017
|
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
|
|
0
link
|
jbrooksga Posts: 6
8/24/2017
|
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.
|
|
0
link
|
sseib Posts: 1
9/13/2017
|
Is there any documentation on how to setup Blox to work with ShoreTel. I am new to this and really dont have any idea where to start.
|
|
0
link
|
bloxsupport1 Posts: 232
9/13/2017
|
Please follow the user manual and configuration guide to setup the blox. Below is the link to download the manuals
https://drive.google.com/open?id=0B5hujoHXcrfGbkIzdmJudHVOU1E
sseib wrote:
Is there any documentation on how to setup Blox to work with ShoreTel. I am new to this and really dont have any idea where to start.
|
|
0
link
|
wreckroot Posts: 3
2/9/2018
|
jbrooksga wrote:
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.
Having the same issue. Inbound and Outbound calls work with audio as expected but Outbound calls drop at 30 seconds. Packet trace shows the outbound acks are sent to the domain name of the trunk instead of the IP the call is associated with. Is there a way to fix?
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.6-19.x86_64 blox_rtpengine-1.0.4-8.x86_64
|
|
0
link
|
bloxsupport1 Posts: 232
2/11/2018
|
@wreckroot: can you upgrade to recent version and try again You can download upgrade package from https://blox.org/downloads
Existing user can download updates here Blox 1.0.6-19 : Download (File Size: 7.62MB)
|
|
0
link
|
wreckroot Posts: 3
2/12/2018
|
bloxsupport1 wrote:
@wreckroot: can you upgrade to recent version and try again
Upgrade to the latest version but same results.
blox_core-1.0.6-19.x86_64 blox_opensips-1.0.6-19.x86_64 blox_rtppinhole-1.0.6-19.x86_64 blox_ministun_client-1.0.6-19.x86_64 blox_security-1.0.6-19.x86_64 freeblox-1.0.6-19.x86_64 blox-rpm-keys-1.0.6-19.x86_64 blox_rtpengine-1.0.6-19.x86_64
I had the internal SIP domain using the IP of the Shoretel and the external SIP domain using my public address. I then changed the internal SIP domain to use the inside IP of the SBC, but no change. edited by wreckroot on 2/12/2018
|
|
0
link
|
bloxsupport1 Posts: 232
2/13/2018
|
Please mail us the backup config of Blox, Tools-->Administration, click on Config Backup.
Send it to support@blox.org
Thanks and Regards Blox Support Team
wreckroot wrote:
bloxsupport1 wrote:
@wreckroot: can you upgrade to recent version and try again
Upgrade to the latest version but same results.
blox_core-1.0.6-19.x86_64 blox_opensips-1.0.6-19.x86_64 blox_rtppinhole-1.0.6-19.x86_64 blox_ministun_client-1.0.6-19.x86_64 blox_security-1.0.6-19.x86_64 freeblox-1.0.6-19.x86_64 blox-rpm-keys-1.0.6-19.x86_64 blox_rtpengine-1.0.6-19.x86_64
I had the internal SIP domain using the IP of the Shoretel and the external SIP domain using my public address. I then changed the internal SIP domain to use the inside IP of the SBC, but no change. edited by wreckroot on 2/12/2018
|
|
0
link
|