- Joined
- Oct 30, 2008
- Messages
- 5
- Reaction score
- 0
Hi all,
So here is my problem. In less than a week I need to demo a 3cx solution to a potential client. I have setup things in my office and home to simulate the environment in which 3cx will be used in production. Rather than 20 paragraphs trying to explain the topology, I have attached a drawing. Please excuse my total lack of Visio Skills.
Here is the problem I am running into:
X100 can call the pstn and x103, but not x101 or x102 (x100 shows as dialing in status)
X101 can call 100 and it will ring, but the only sound that works is hold music. X102 does not ring, PSTN and x103 are fine.
X102 can call x100, x103, PSTN, and all is fine. X101 never rings.
X103 can call the pstn no problem. X100 and x102 will work when they feel like it and x101 never rings.
The PSTN can call x103 ok. X100 and x102 will work when they feel like it and x101 never rings.
To make things more interesting “client office” will actually have ~24 phones and 4-6 soft phones. They will connect to the PSTN via Sprint(Pots lines) and Televox(sip trunks), for various reasons not very interesting.
Anticipated questions:
How do you connect to pstn?
Quintum gateway. Yah, I know. It’s getting replaced.
What router is at “client office”
They have a Linksys BEFSR41. Same thing I’m using to test. I’ve also tried a pix 501 and a Dlink something. Same result with each. Only difference is the frequency in which x101 and x102 will work when calls come in from PSTN or X103.
How is the 3cx server on the internet?
It has a single public IP (I have about 400 available if this helps) and is protected by a Linux box acting as a firewall. The firewall is passive and only restricts port access. No filtering or packet IDing is being done. The connection is an oc48 with 50Mbit available to the 3cx server (kill mosquito with canon concept).
Is everything really on the same Class B segment?
Yep. I'm sitting on the backbone of a rather large provider.
Thank you all very much in advance!
-Jason
So here is my problem. In less than a week I need to demo a 3cx solution to a potential client. I have setup things in my office and home to simulate the environment in which 3cx will be used in production. Rather than 20 paragraphs trying to explain the topology, I have attached a drawing. Please excuse my total lack of Visio Skills.
Here is the problem I am running into:
X100 can call the pstn and x103, but not x101 or x102 (x100 shows as dialing in status)
X101 can call 100 and it will ring, but the only sound that works is hold music. X102 does not ring, PSTN and x103 are fine.
X102 can call x100, x103, PSTN, and all is fine. X101 never rings.
X103 can call the pstn no problem. X100 and x102 will work when they feel like it and x101 never rings.
The PSTN can call x103 ok. X100 and x102 will work when they feel like it and x101 never rings.
To make things more interesting “client office” will actually have ~24 phones and 4-6 soft phones. They will connect to the PSTN via Sprint(Pots lines) and Televox(sip trunks), for various reasons not very interesting.
Anticipated questions:
How do you connect to pstn?
Quintum gateway. Yah, I know. It’s getting replaced.
What router is at “client office”
They have a Linksys BEFSR41. Same thing I’m using to test. I’ve also tried a pix 501 and a Dlink something. Same result with each. Only difference is the frequency in which x101 and x102 will work when calls come in from PSTN or X103.
How is the 3cx server on the internet?
It has a single public IP (I have about 400 available if this helps) and is protected by a Linux box acting as a firewall. The firewall is passive and only restricts port access. No filtering or packet IDing is being done. The connection is an oc48 with 50Mbit available to the 3cx server (kill mosquito with canon concept).
Is everything really on the same Class B segment?
Yep. I'm sitting on the backbone of a rather large provider.
Thank you all very much in advance!
-Jason