Can't Receive Inbound calls on SPA-3102 on 3CX

[ziptalk]

Istill have this problem. SPA-3000 setup and working in about 10-15 mins. SPA-3102, several days tweaking settings, following 3CX instructions and numerous posts to no avail. I bought two of the units with the intention to have one as a hot-spare and part of my test/lab kit, and the other to deploy at a remote site. The ability for a home worker (in this instance myself whilst testing), I need the remote extension to be able to use it's own local PSTN. I have achieved this and out-bound calls are fine, yet inbound calls despite reaching the SPA-3102 does not seem to generate the necessary SIP traffic to the 3CX to signal the incoming call.For what it's worth the remote extension can call out and receive calls fine over the VPN from and to various locations, so the RIP for routing is all sound ruling out a networking problem. I can only deduce the fault to be at the SPA-3102 and suspect a misconfiguration, either way I can swap test the hardware to eliminate the unit itself being broken. Wjen I get back from hols I will factory reset and setup again from scratch and with fresh eyes. The only thing making me persevere here is that if others can get it working then I know the unit can be made to work. Agree with the amount of noise about this issue, I'll be interested on 3CX commenting on their views above it being supported. Experience counts for everything and it's clear there's a few of us out there struggling with this unit!

 

[leejor]

I have achieved this and out-bound calls are fine, yet inbound calls despite reaching the SPA-3102 does not seem to generate the necessary SIP traffic to the 3CX to signal the incoming call.

Are you saying that incoming calls from the PSTN (FXO) port aren't ringing the set plugged into the FXS port?


Check the settings under PSTN > PSTN-to-VoIP Gateway Setup > PSTN to VoIP gateway enable (NO) as you aren't going to try sending calls back to a 3CX trunk, PSTN ring thru Line 1 (YES),PSTN ring thru delay (3) if you are receiving Bellcore type caller ID, otherwise you can lower that,

Make sure you don't have any PSTN to VoIP authorisation enabled.

 

[voipoint]

Another person with problem on SPA3102

The gateway is log in on the system. I have green light on the line in 3CX.
I can make call thru PSTN on SPA but I cannot receive the calls properly.

When I’m dialing from my mobile phone PSTN number I hear the signal, than the LED(line) is starting blinking on SPA, and then I hear another type of signal, straight …after 10-15s connection breaks. When I’m trying to dial the ext number the connection is establish and ext rings.

But … I set up the calls to ring directly on exact ext and this doesn’t work

Any idea what’s wrong and what I’m missing?

Product Name: SPA-3102
Software Version: 5.1.10(GW)
Hardware Version: 1.4.5(a)

Thanks in advance for help!

 

[voipoint]

PS: one more question…why I cannot set the call coming from SPA to ring group or digital receptionist?

 

[voipoint]

OK I solve the problem with incoming calls:

From the guide on 3CX WWW

In the PSTN-To-VoIP Gateway Setup section:
e. Set the "PSTN Caller ID Pattern" field to "*". <--- This line should be blank! without "*"

The calls are working fine.
I got the problem with voice coming out from my mobile...the ext on my PBX don't hear PSTN line.
The other side hear ext from the PBX.

For me is a little bit strange…I have to change ports on SPA3102? Any idea why PBX don't hear voice from PSTN?

 

[adriaan]

I agree with Ziptalk that this unit gives enough of us trouble that 3CX should get involved in the discussion. How can we draw their attention to this and get the matter finally resolved?

 

[jms4318]

Voipoint,

Weeks trying configurations, inpedance, ringings, ampliud. And a simple * solution all the problem.


THANKS !!!!! this is a GREAT forum

 

[Ping_it]

I too have been "challanged" trying to configure the SPA-3102 with 3CX and have worked on and off attempting to get it to make and receive calls. I was about to give up on the process until I came across this posting with the suggestion to remove the "*" configuration script for "PSTN Caller ID Pattern". Once I followed that suggestion, voila, it worked. Both inbound and outbound calling. :cry: :lol: :x Hopefully, someone here will "adjust" the posted SPA-3102 configuration to reflect this change so others will not have to waste time with this misinformation. I would hate to count the hours I have spent attempting to configure the SPA-3102 with 3CX. And to have it be because of this one small character in the posted instructions. My thought was to replace a Linksys Voice System with 3CX but was having doubts as to the decision. At least now that it is working I can test the system and compare to the Linksys PBX which I have used for over a year without any issues. Hopefully, the testing of 3CX will be smoother now that this initial hurdle has been jumped. Still some what miffed at this "Asterisk" error. Was it intential? :?: :roll: Many thanks to the person who "discovered" this issue. Congratulations and much appreciation. :lol: 8) :lol:

 

[adriaan]

I, like Ping_it, have spent days on this problem and agree with him that somebody should rectify the (incorrect) instructions issued by 3CX to avoid other users having to waste the same amount of time that we have on this problem. Pity that 3CX did not get involved earlier. How do we bring this matter to their attention?

A big thank you to Voipoint for solving this problem and getting me out of my mysery.

Thanks guys

 

[voipoint]

Hi to all

Many thanks for good word I was fighting with that 2 nights . Customer who order PBX was killing me and my team and we didn’t know the solution.
But … finally it’s working … so enjoy …

Right know it’s time to find solution for faxes. I had some problems with fax signal on 3CX. We are almost at the end to find good configuration on SPA3201 ( the one from 3CX also doesn’t work)

Enjoy 

 

[Ysterlong]

I am also from South Africa.

I have installed a 3CX PBX with 4 x SPA3102's about two years ago. It took me about half an hour to configure and it was running smoothly. Last week Friday, Telkom changed my incoming lines from ISDN to normal lines and suddenly my 3102's could not pass through incoming calls. I have spent a full two days trying to solve the problem and after hours of randomly fiddling with the PSTN settings, I got it to work again. Please do not ask me what I have done - but it worked. Some of the settings I have changed does not make sense at all, but at least it worked.

Herewith some screen shots of settings that work right now, but I am still busy with fine tuning. Perhaps this might help you get going so long. I must just mention - the problem is not with the 3CX server, but with the Linksys SPA3102 setup.

 

[leejor]

So...you had a box at your location that gave you two analogue phones lines from the NT1?

When working on these, or any other browser based device with LOTS of settings, I find it a good idea to do a "save page as" and keep a copy to print out, of all the "previous" setting. Then you aren't guessing, when you make some changes and things suddenly stop or start working.