Toggle sidebar Toggle sidebar

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

Status
Not open for further replies.
Hello,
the wrong in settings is
you set poth pstn line and line one to 10000
they must be defferent
 
Hi,
If you are saying that I have the same AuthID in both "Line 1" and "PSTN Line" then that is incorrect.

Firstly in "Line 1" I have set
Line Enable=No
I assume that this would mean that is not used.
But just to make sure the AuthID in the "Line 1" Tab = 130

Any other suggestions?
 
Hello,
the screen shots you post line 1 enabled and registerd
 
Hello, i am having the same problems too. I can make calls over the PSTN network from the VOIP phone. However when i recieve an incoming call, nothing happens. There are no entries in the 3CX log either. I have tonight gone through the guide again, and double checked all of the settings. All appear okay. The only one that i'm not too sure on is within 3CX. The PSTN Port Identification. I have this set to 10001, i've kept it the same as the Virtual Extension number, and username and password. Is this okay? Also i have installed the KIWI sys logger. Pointed the SPA at the IP address of it, and enabled logging, but i don't see any logs as yet, is there anything else i need to do. I have put the logger on the 3CX server, is this okay aswell??

Thankyou
Chris
 
Hi,

Have you changed the default settings for the delay to answer. I think the default is 16 seconds.

By default, the SPA-3102 will wait for 16 seconds before delivering a call to a SIP device. To change this, go to the "FXO Timer Values (sec)" section, and change the "PSTN Answer Delay" field to 0. This will set the gateway to answer calls immediately.


Jonathan Hamon
 
Hello, if that question is meant for myself, yes I have.

Chris
 
Chris
I haven't tried running Kiwi on the same PC as 3CX, unless it's trying to use a port that 3Cx is, it "should" work. If you've enabled the syslog level and pointed to the IP you should start seeing the logs. If you can, start it up on a second Pc and see it that makes the difference.
 
I am still struggling to get 3CX to receive the incoming calls (have changed my configuration so many times that I cannot even make outgoing calls which I could do befor). Now see that there are more people having the same problem. I have checked SPA3102 settings over and over from 3CX setup guide (not written in "dummies" mode) and also from screenshots supplied to me by forum member of working system without any luck. I would hate to abandon 3CX and look at something else (eg Asterisk) and would really like to get 3CX working. I have hoewever spent days on this now without any luck and I am getting a bit frustrated.

I am starting to think that maybe something is wrong in my 3CX setup. Would somebody with a working system not consider posting screenshots of both their 3CX and SPA3102 settings which can be used to get a starter system going? This will really be appreciated.

Thanks for all the help thus far.

Adriaan

PS The 3CX system seems to be great software but I have never struggled to get something to work like this before (and I have installed reasonable sized networks etc). Any help, ideas or assistance will be greatly appreciated.
 
Okay I have my syslog working now. Just had to change the syslog level on the SPA from 0 to 3. It does work on the same device as 3CX, uses different ports.
Here is my log when I call in, I called in twice.

08-18-2009 22:07:04 Local2.Debug 192.168.1.14 FXO:Stop CNDD
08-18-2009 22:07:04 Local2.Debug 192.168.1.14 AUD:Stop PSTN Tone
08-18-2009 22:07:04 Local3.Debug 192.168.1.14 FXO:On Hook
08-18-2009 22:07:04 Local2.Debug 192.168.1.14 AUD:Stop PSTN Tone
08-18-2009 22:06:40 Local2.Debug 192.168.1.14 FXO:Start CNDD
08-18-2009 22:06:40 Local2.Debug 192.168.1.14 FXO:OnHook PolRev
08-18-2009 22:06:40 Local2.Debug 192.168.1.14 POL REV 40 -50
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 <010>
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:XMNODE = 1024 (1024 112)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:STUNTS = 16 ( 16 68)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:SUBDLG = 2 ( 2 6444)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:SIPLIN = 0 ( 2 140)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:SIPREG = 3 ( 4 296)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:SIPSES = 12 ( 12 9520)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:SIPDLG = 10 ( 10 148)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:SIPAUS = 7 ( 8 588)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:SIPSTS = 32 ( 32 6620)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:SIPCTS = 32 ( 32 1140)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:SIPCOR = 0 ( 1 28)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:TIMEOU = 111 (120 52)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:RTPTXB = 64 ( 64 108)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:RTPREB = 40 ( 40 48)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 OP:RTPRXB = 96 ( 96 192)
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 --- OBJ POOL STAT ---
08-18-2009 22:06:11 Local2.Debug 192.168.1.14 CC:Clean Up
08-18-2009 22:05:38 Local2.Debug 192.168.1.14 FXO:Stop CNDD
08-18-2009 22:05:38 Local2.Debug 192.168.1.14 AUD:Stop PSTN Tone
08-18-2009 22:05:38 Local3.Debug 192.168.1.14 FXO:On Hook
08-18-2009 22:05:38 Local2.Debug 192.168.1.14 AUD:Stop PSTN Tone
08-18-2009 22:05:23 Local2.Debug 192.168.1.14 FXO:Start CNDD
08-18-2009 22:05:23 Local2.Debug 192.168.1.14 FXO:OnHook PolRev
08-18-2009 22:05:23 Local2.Debug 192.168.1.14 POL REV 47 -48

Hope this helps
Chris
 
I'll have to have a look at what an incoming call looks like on mine. Is the line ringing during the time between 22:05:23 and 22:05:38 , and then just dies?
 
Well I am calling from my mobile phone into my the PSTN system that has the 3CX system on it. Yes, I can hear the line ringing on the mobile phone, and other POTS phones do ring too, but nothing on 3CX, nothing in the logs either.


Chris
 
Didn't have time to look at mine last night....
Does the line just continue to ring? It's strange that even when registered, the 3102 isn't sending anything to 3CX when a call comes in. Did you disable the FXS circuit on the 3102 as it was data filled with the same number as the FXO line and did show enabled in you screen shot?
 
It's really not supposed to be this difficult! I was looking back at some of the other SPA3102 related posts I have made in the past trying to help other users - but what I can say is that when everything is set up correctly it works fine, mine has performed perfectly for well over 2 years now.

My suggestion in cases where there is uncertainty about whether it is 3cx or an SPA3102 configuration issue is to do a packet capture. If you install Wireshark on your 3cx machine and set it to capture all SIP traffic (capture filter to 'port 5060') then it is pretty easy to follow the SIP packets to see exactly what is going on since Wireshark does much of the hard work decoding them. If you start capture before making an incoming call and stop when you hang up then there will probably not be too much to go through. It certainly enabled me to figure various issues when I started up! The SPA3102 syslog dump is pretty complex to understand, give me Wireshark any time!

Just a thought, though I realise it is not always possible to run Wireshark on a 3cx machine.

Chris
 
This is what i get on an incoming call (in syslog)....

08-20-2009 07:08:58 Local2.Debug 192.168.248.206 DLG Terminated 29c958
08-20-2009 07:08:58 Local2.Debug 192.168.248.206 CC:Ended
08-20-2009 07:08:58 Local2.Debug 192.168.248.206 [0]AUD Rel Call
08-20-2009 07:08:58 Local3.Debug 192.168.248.206 [0]FM Alert Stop RxTx (c=0024a404;a=0)
08-20-2009 07:08:58 Local2.Debug 192.168.248.206 [1]AUD Rel Call
08-20-2009 07:08:58 Local3.Debug 192.168.248.206 [0]FM Alert Stop RxTx (c=0024fe9c;a=0)
08-20-2009 07:08:58 Local2.Debug 192.168.248.206 FXO:Stop CNDD
08-20-2009 07:08:58 Local2.Debug 192.168.248.206 AUD:Stop PSTN Tone
08-20-2009 07:08:58 Local3.Debug 192.168.248.206 FXO:On Hook
08-20-2009 07:08:58 Local2.Debug 192.168.248.206 AUD:Stop PSTN Tone
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 [1]RTP Rx Dn
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 AUD:Play PSTN Tone 9
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 CC:Ringback
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 [0]RTP Rx Up
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 [0]AUD ALLOC CALL (port=16444)
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 [1]RTP Rx Up
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 [1]AUD ALLOC CALL (port=16442)
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 Calling:[email protected]:5060
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 AUD:Stop PSTN Tone
08-20-2009 07:08:42 Local2.Debug 192.168.248.206 AUD:Stop PSTN Tone
08-20-2009 07:08:41 Local3.Debug 192.168.248.206 FXO:CNDD Name=PRIVATE Phone=6XXXXXXXXX
08-20-2009 07:08:41 Local2.Debug 192.168.248.206 FXO:Stop CNDD
08-20-2009 07:08:41 Local2.Debug 192.168.248.206 FXO:CNDD name=PRIVATE , number=6XXXXXXXXX
08-20-2009 07:08:39 Local2.Debug 192.168.248.206 FXO:Start CNDD

If all else fails it could be some sort of corruption. You might try a factory reset and then just datafilling the PSTN line.
 
Has anybody perhaps resolved this problem yet? I am at my wits end!!

With the help of a very good forum user (thanks George for all your help so far) here in SA I have created an exact similiar setup (from backups supplied) as his working system and the problem still persists. From the posts above it seems that there are quite a few people out there having the same problem. The SPA3102 (or is it 3CX) seems to be really a "problem child". I cannot however understand why it works in some instances and in others not.

I would still like to get 3CX working (before I am forced look at other solutions) and any help will be greatly appreciated.
 
Adriaan,
I to am having the same problem (in Australia).
The SPA-3102 is widely used in Australia by a number of VOIP providers (notably Engin).
I want to be able to get 3CX up and running at home before I try it at the office with ISDN (I'll purchase a dedicated gateway for that).
This seems too hard and there are way too many posts for this to be mainstream.

With years of background in windows, I thought 3CX would be simpler. Yet I was able to get Trixbox (linux based) up and going in no time flat.

The other thing that seems to be lacking in 3CX is any sort of Permissions based dialling. I've looked all over and cant find anything that prevents any extension dialling any number.
 
Hi Lorenzo

I must agree that this is far to big a problem. I have now spent days on this and thought it should have been a lot easier. I do not think (I might be wrong) that I am to stupid either as I have many years experience in the IT industry and have already installed some sizeable networks for example. This is however getting me down.

I do not really want to look at the Linux route as I have NO experience of this and support here (South Africa) is not very strong for Linux (whilst we have a lot of experts in Windows). I am afraid that if something goes wrong in Linux I will not be able to resolve it (and that no help will be available) and cannot afford for my telephone system (once working) to be down indefinately.

I further problem is that I enquired with my supplier of the SPA3102 (there are authorised Asterisk distributors) and they tried to setup the SPA with Trixbox. Bad news is that after days of struggling they reported that "the SPA does not work with Trixbox". I would have thought that they are the experts and it is interesting to me that you say it was easy to run the SPA with Trixbox.

I really do not know what to do anymore.

Regards
Adriaan
 
Sorry to hear of the troubles that you are having with the 3102. I don't know what to say, they are exteremely flexible devices and as such , have far too many options for most people. Luckily, there are only a limited number that need to be changed to get it working with 3CX, along with some regional settings unique to each counrty.
I take it you guys downloaded and went over the Admin manual?
I know that when i got my first SPA3000 a few years back, I read the manual for that from front to back to make sense of what the options actually did and how the device worked. In the next few months i hope to get another 3102 and do a step by step configuration guide for 3CX, if time allows. My devices (3000 & 3102) have gone from being used on FWD, SipPhone, and then on to 3CX without a factory reset in between. It's very frustrating to try to troubleshoot things over the net.

As far as this question...
LorenzoM said:
The other thing that seems to be lacking in 3CX is any sort of Permissions based dialling. I've looked all over and cant find anything that prevents any extension dialling any number.
Click to expand...

When you build outbound rules you can specify which extensions (or a range) they apply to. You could have one extension dial 9+ and go out one route and another dial the same and go out another. There doesn't appear to be a way (other than in the dialplan of device itself) to block extensions calling other extensions. In an office environment, this feature really doesn't make sense for the majority of users.
 
I am not the type that give up easily but must admit that I am "down and out" about this one :cry: . I can assure you that I have (even before asking for help on this forum) checked each and every little bit of information (including manuals) I could get. The strange thing is that after days of struggling I have restored a backup (3CX and SPA) from a working system and still have exactly the same problem (cannot receive incoming calls). It thus means that both 3CX and SPA must be setup correctly. The only thing that I can still think of is that there is a difference in Windows settings somewhere that 3CX is not happy with. Is this perhaps possible? Any ideas :idea: ?

:x :evil:
 
I would, perhaps, suspect Windows if the calls were showing up in the 3CX logs but not going any furthur. Having 3 places ( 3102 syslogs, Wireshark on the Ethernet link and 3CX system logs) that you can see the "progress' of a call from the 3102 to 3CX should allow you determine at which point it's failing. If the 3102 isn't even attempting to send out a call to the 3CX, then , other than a faulty 3102, it has to be one of the settings. Have you tried changing the settings to get an incoming PSTN call to ring the FXS port directly, just as a starting point?
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,884
Messages
589,542
Members
164,741
Latest member
Carsonix
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom