- Joined
- Jun 25, 2008
- Messages
- 24
- Reaction score
- 0
I note that the SPA3102 gateway has been re-written for v7.1 and think this might be the reason for my problems.
I have just configured a new 3CX server on v7.1 in an identical way as an earlier v7.0, with a Linksys SPA3102 providing a PSTN Gateway.
Using an identical configuration as on the SPA3102 as I had historically used, I was unable to get incoming calls to even register in the 3CX system. To confirm that I wasn't going silly, I even swapped a SPA3102 from the 7.0 system to the 7.1.
What I eventually found in the SPA3102 configuration, I had to set the PSTN Answer Delay: to either 0 or 1 to allow incoming calls to register. Any higher and it wouldn't work. The downside to this is that CID no longer works, as it need a setting of at least 2 to give the system long enough to extract this data.
Also another unearthed couple smaller faults. When you create a new SPA3102 gateway, the 3CX defaults to port 5062. This is not open, even when the configuration is saved, but port 5061 is. I had to manually reset the port to 5061 on the 3CX to make it work. (setting both 3CX and SPA3102 to 5062 isn't any good. Also I noted that the generated config file, still persists in using port 5062 - even though its been set to 5061 on the 3CX
Can anyone else confirm my findings? Can an update be provided soon Please!
So in summary, with a little manual tweaking, I now have incoming calls from the PSTN, but no CID being delivered.
John
I have just configured a new 3CX server on v7.1 in an identical way as an earlier v7.0, with a Linksys SPA3102 providing a PSTN Gateway.
Using an identical configuration as on the SPA3102 as I had historically used, I was unable to get incoming calls to even register in the 3CX system. To confirm that I wasn't going silly, I even swapped a SPA3102 from the 7.0 system to the 7.1.
What I eventually found in the SPA3102 configuration, I had to set the PSTN Answer Delay: to either 0 or 1 to allow incoming calls to register. Any higher and it wouldn't work. The downside to this is that CID no longer works, as it need a setting of at least 2 to give the system long enough to extract this data.
Also another unearthed couple smaller faults. When you create a new SPA3102 gateway, the 3CX defaults to port 5062. This is not open, even when the configuration is saved, but port 5061 is. I had to manually reset the port to 5061 on the 3CX to make it work. (setting both 3CX and SPA3102 to 5062 isn't any good. Also I noted that the generated config file, still persists in using port 5062 - even though its been set to 5061 on the 3CX
Can anyone else confirm my findings? Can an update be provided soon Please!
So in summary, with a little manual tweaking, I now have incoming calls from the PSTN, but no CID being delivered.
John