• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

CallerID with a SPA3000

Status
Not open for further replies.

paultilley100

Joined
Sep 14, 2010
Messages
4
Reaction score
0
Hi all

I hope somebody can shed some light on my problem.....

I have a SPA3000 with my BT line plugged into it and it is connected to 3CX on port 10001.
The SPA3000 detects the incoming CallerID (looking in the web config shows 'Last Caller ID') correctly.

However, when the call comes through to my Grandstream GXP2000 handsets, the handset display shows Sipura 10001, not the CallerID.

Any ideas of what I have done wrong?

Thanks in advance.
Paul
 
Post, or just have a look at, the 3CX log showing the incoming call. That will show whether or not the caller ID is being passed onto 3CX.
 
OK - this might sound daft, but I know Asterisk pretty much inside out. 3CX is new to me - how do i get the log?
 
ok - stupid me - ive found them - looking now.......
 
23:58:28.358 [CM503025]: Call(5): Calling Ext:Ext.99@[Dev:sip:[email protected]:40600;rinstance=4423ec9c2c5c8f52]
23:58:28.296 [CM503004]: Call(5): Route 1: Ext:Ext.99@[Dev:sip:[email protected]:40600;rinstance=4423ec9c2c5c8f52]
23:58:28.296 [CM503010]: Making route(s) to <sip:[email protected]:5060;user=vmail>
23:58:28.296 [CM505002]: Gateway:[Sipura] Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3000-3.1.10(GWd)] PBX contact: [sip:[email protected]:5060]
23:58:28.296 [CM503001]: Call(5): Incoming call from 10001@(Ln.10001@Sipura) to <sip:[email protected]:5060;user=vmail>
23:58:28.280 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10001 forwards to VM:21
23:50:49.245 [CM503007]: Call(4): Device joined: sip:[email protected]:40600;rinstance=4423ec9c2c5c8f52
23:50:49.245 [CM505001]: Ext.99: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:[email protected]:5060]
23:50:49.104 [CM503025]: Call(4): Calling Ext:Ext.99@[Dev:sip:[email protected]:40600;rinstance=4423ec9c2c5c8f52]
23:50:49.042 [CM503010]: Making route(s) to <sip:[email protected]:5060;user=vmail>
23:50:49.026 [CM503001]: Call(4): Incoming call from 10001@(Ln.10001@Sipura) to <sip:[email protected]:5060;user=vmail>
23:43:25.088 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 96.9.132.83:3478 over Transport 10.0.0.100:5060
 
paultilley100 said:
23:50:49.026 [CM503001]: Call(4): Incoming call from 10001@(Ln.10001@Sipura) to <sip:[email protected]:5060;user=vmail>

Well, unfortunately, the 3000 isn't passing the caller ID onto 3CX. Because you are in the UK, there may be different reasons when compared to Caller Id in North America, but, off hand I suspect that the call info is being sent onto 3CX before the caller ID has been acquired, Something that happens here as well, with the wrong setting. I'm assuming that you have the caller ID set for BT specs, as you said that it was showing in the 3000 menu. Go to the PSTN tab/FXO Timer Values/PSTN Answer Delay. the default here is 16 seconds, which is far too long. However if you set it to short, like 1 or two seconds, then the call is passed onto 3Cx before it has a chance to get the caller Id info. Try about 7 seconds and then reduce the time until it fails. In North America anything less than 3 seconds means no caller ID.
 
Status
Not open for further replies.
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.