Trixbox Pro issue connecting to server via trixbox.fonality.com
Submitted by jestoner on Wed, 10/08/2008 - 12:31pm.
Greetings,
My Issue:
I can't reach my server at s######.trixbox.fonality.com outside of my local network. I have two LANs (with different subnets and external IPs) at work and have moved the Trixbox from one to the other. In both cases I've been able to reach the server inside the LAN at s######.trixbox.fonality.com. However, once I try from outside the LAN I can't reach it.
What I have tried to resolve the issue:
I searched and found a trouble shooting guide that closely parralleled my issue. Using the guide and logging in the ip admin I pinged the gateway, 4.2.2.2 and the fonality vpn. Each time I received a rapid response of under 25msec. For no other reason then kicks and giggles I changed the DNS servers on the Trixbox to 4.2.2.# but that did not resolve the issue.
My environment:
LAN 1 - Simple LAN connected to a Linksys Router with DHCP Server enable behind a Linksys Cable modem.
LAN 2 - Small Business Server with DHCP server enabled behind a Sonicwall TZ170 with DHCP server disabled (a few ports ports open for server functionality) behind a Speedstream DSL modem.
About my Trixbox:
Dell Optiplex 550 3.0Ghz 1.5Gig Ram. This is a test environment before I move to a working deployment. I've setup one extension although there are no phones nor any telephony cards installed. I will max out the TrixBox Pro SE version with 10 phones and do additional testing on FXO/FXS cards prior to deployment.
My conclusion:
There is a mystery setting that I'm missing on the Trixbox. I'm thinking I need to set something to "stupid noob" at it will work.
About Me:
I'm an advanced user with knowledge in Windows Small Domains and Avaya Phone Systems. I have a novice amount of knowledge about linux (mainly Ubuntu) I'm a complete Newbie when it comes to Trixbox.
Any suggestions are welcome
 
I am assuming you are trying
Wed, 10/08/2008 - 1:39pm
I am assuming you are trying to connect a phone to trixbox from outside your network. You need to change the s######.trixbox.fonality.com to s######x.trixbox.fonality.com. The "x" tells it to lookup the external IP instead of your internal address.
Second you must allow several ports threw your firewall to get connectivity. Do a search in the wiki at http://help.trixbox.com for your ports.
 
Well that was easy! Thanks
Wed, 10/08/2008 - 2:10pm
Well that was easy! Thanks - I keep thinking it wasn't port issue becuase the VPN1, silly me, I thought the CentOs must be some powerful stuff. And I'm sure it is once the proper ports are forwarded. Thanks
 
Well I spoke to soon. I've
Thu, 10/09/2008 - 11:29am
Well I spoke to soon. I've got the following ports open and forwarding to the Trixbox but still no luck.
Remote SIP Registration (UDP 5060)
Remote SIP Audio (UDP 10000-20000)
Remote IAX2 Registration and Audio (UDP 4569)
Remote HUD2 (Uses IRC - TCP 6600)
Remote HUD3 (Uses Jabber - TCP 5222)
Additionally I've placed the Trixbox into the DMZ so ALL ports are now open and forwarding to the Trixbox. I can hit the Trixbox via the external IP, but still can reach it via http://s######.trixbox.fonality.com/
What am I missing?
 
What type of phone are you
Thu, 10/09/2008 - 12:11pm
What type of phone are you trying to connect?
UDP 3000-4000 is signalling for Aastra phones.
UDP 9710-20000 is signalling for Softphones.
From outside the network you need to use http://s######x.trixbox.fonality.com <----Notice the "x" after the s######.
Make sure to disable any SIP fixup that your firewall may be using.
 
The issue is not phones, but
Thu, 10/09/2008 - 2:50pm
The issue is not phones, but the Trixbox server itself.
I can't get anything to come up when I point my web browser to http://s######.trixbox.fonality.com. However when I point my web browser to the external IP I can connect to my local Trixbox.
I'm thinking there is some issue on the Trixbox, perhaps its not updating at server at fonaility.
 
Correction
Thu, 10/09/2008 - 8:59pm
Quote:
UDP 3000-4000 is signalling for Aastra phones.
UDP 9710-20000 is signalling for Softphones.
Do you guys just sit around and make this stuff up?
Standard SIP port (signaling) is UPD:5060
Standard RTP Port (media) is UDP:10000-20000
--
Scott
aka "Skyking"
 
From aastra online
Fri, 10/10/2008 - 6:25am
From the site at http://www.aastraonline.com/index.php?option=com_content&task=view&id=11...
****Pay attention to the last line****
# (Alternate Approach) Set up port forwarding in your router/firewall.
1. This configuration can be very complicated, and it will not work with all routers. Some routers are simply not SIP compatible. This approach is not recommended unless you have experience configuring network firewalls.
2. Aastra Online's IP phones use the SIP protocol for digital call signaling. The actual voice audio uses the RTP protocol. The port number is dynamically negotiated in the SIP signaling by the device. Routers and firewalls that are SIP aware will automatically proxy the correct RTP ports for SIP calls.
3. Both the SIP protocol and the RTP protocol must be allowed. SIP uses UDP/5060.
4. The exact RTP port numbers vary from phone to phone. These are the port ranges for each phone type Aastra Online sells. Note that these may change between firmware versions, so we suggest using a packet trace tool like Ethereal to verify what your phones are actually using.
Aastra = UDP/3000 - UDP 4000
 
Thank you Brandon,SkykingOH
Mon, 10/13/2008 - 7:53am
Thank you Brandon,
SkykingOH wrote:
Quote:
UDP 3000-4000 is signalling for Aastra phones.
UDP 9710-20000 is signalling for Softphones.
Do you guys just sit around and make this stuff up?
All of this information was also posted in the trixbox wiki, they just changed to a new wiki and the old page is not there anymore. Also if you do a search on these forums you will find several threads with the same information posted by fonality engineers.
jestoner if you are still having issues please let us know.
 
This has been one of the
Tue, 10/14/2008 - 6:18am
This has been one of the screwier experiences I have had.
The issue had always been that I could reach my server at http://s133822.trixbox.fonality.com/ (I can share this address now since I yanked the install) I'm guessng it was a problem with the install since I open all ports to the Trixbox and the issue remained. But somehow everyone thought I was talking about phones, even though I said "The issue is not phones, but the Trixbox server itself".
Its clear to me that right now Trixbox is not ready for my type of user. And since I'm not willing to plunk down thousands of dollars nor commit myself to recurring cost I will wait for the next version of CE and see if its better. Until then I will look at other IP PBX options. My issue is that I've never been impressed with service from Business Telco providers and I don't care to go into IP solutions without being able to maintain it myself.
Until the next realease...good luck.
 
Did you try to access the
Wed, 10/15/2008 - 5:53am
Did you try to access the system from outside your network with this address? http://s133822x.trixbox.fonality.com
What exactly are you trying to do if not connect phones to it? Access the control panel? If so you do that at http://cp.trixbox.com
 
Member Since:
2008-10-08