SPA 3102 caller ID not working

Unanswered Question
Aug 8th, 2009

Hi,

I'm having trouble getting CID to work with my SPA 3102. I'm using SIP to call out (Voipbuster) and using the PSTN line to receive calls. When I switch off the SPA 3102, CID works fine on my incoming calls. I think I've tried every setting I think off (visited many forums):PSTN Ring Thru Delay, Caller ID Method, PSTN CID For VoIP CID = Yes, went back to the factory default, installed the lastest firmware 5.1.10, etc. In the info tab everytime the Last PSTN caller only shows a , .

I've captured some logging information of an incomming PSTN call, see attachment.

Any ideas on how I can get CID to work, thanks.

Edwin

Netherlands

Attachment: 
I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Patrick Born Mon, 08/10/2009 - 13:33

Hi Edwin,

Does caller id ever work? Does caller id work after a power reset?

Regards,

Patrick

-----------

EdGarritsen Tue, 08/11/2009 - 08:40

Hi Patrick,

Thanks for your response.

- Caller ID works with VOIP calls

- Caller ID works when SPA is switched off (PSTN calls)

- Caller ID has never worked with PSTN calls through SPA

I performed a power reset (unplugged the power from the SPA for a couple of minutes) but no caller ID.

The strange thing is that I can see all 10 digits of the caller ID in the spa log, displayed as:

FXO:Digit=0
FXO:Digit=6
FXO:Digit=2
FXO:Digit=9
FXO:Digit=8
FXO:Digit=1
FXO:Digit=7
FXO:Digit=3
FXO:Digit=2
FXO:Digit=1

(I replaced some digits of the actual caller ID)

Regards,

Edwin Garritsen.

EdGarritsen Tue, 08/25/2009 - 13:14

Hi Patrick,

Thanks for the reply.

The problem you are referring to is where the CID is displayed in the beginning and disappears after a few calls. In my case the CID is never displayed on PSTN calls through the SPA3102. Are you sure that the fix the development team is working on is going to fix my problem?

Regards,

Edwin.

EdGarritsen Wed, 08/26/2009 - 13:15

Hi Patrick,

I just sent you an e-mail with the configuration information.


Regards,

Edwin.

Patrick Born Thu, 08/27/2009 - 07:31

Thanks Edwin, I am in receipt of it.

I'll get back to you.

Regards,

Patrick

---------

Patrick Born Thu, 08/27/2009 - 08:04

Hi Edwin,

Please try the following in order to configure your SPA3102 for Netherlands caller ID:

Voice tab > Regional tab > Miscellaneous >

  1. Caller ID Method: ETSI DTMF
  2. Caller ID: [try bell 202]

cap-797.jpg

Voice tab > PSTN Line > International Control >

  1. FXO Port Impedance: 270+(750||150nF)
  2. On-Hook Speed: 3 ms(ETSI)
  3. Current Limiting: yes

cap-796.jpg

Please let me know of your progress.

Regards,

Patrick

----------

EdGarritsen Thu, 08/27/2009 - 12:42

Hi Patrick,

Thanks for the response.

Unfortunately the new settings did not change anything, still no caller ID. The only thing that's different is that before changing these settings the phone displayed "Unknown" as the caller ID and now it displays some strange characters. When I only change the Caller ID method back to ETSI DTMF With PR it shows "Unknown" again in the display.

I have tried another telephone and replaced all telephone cables but that did not help, same result.

I have sent a copy of the log captured during the call with these new settings to your cisco email address.

Regards,

Edwin

Patrick Born Thu, 08/27/2009 - 15:48

Hi Edwin,

Can you please remove the SPA3102 from the line and connect an analog phone capable of receiving CID?

Make a call to the line connected to the analog phone and verify that CID is displayed appropriately.

I know that you mentioned in your first post that this previously worked, but I've previously experienced CID services being halted by the PSTN in the middle of a long CID configuration period.  :-)

While you're verifying that you have CID service, I'll check with my colleagues for some inspiration.

Regards,

Patrick

-----------

EdGarritsen Sat, 08/29/2009 - 08:43

Hi Patrick,

I removed the SPA3102 from the line, connecting the phone directly to the PSTN line, the Caller ID is now displayed when a make a call to the PSTN lijn. The CID service form the telco is OK.

If you need more information please let me know.

Regards,

Edwin.

Patrick Born Mon, 08/31/2009 - 07:43

Hi Edwin,

Thanks for confirming that CID is still working without the SPA3102.

I'm still trying to find a solution for you.

Regards,

Patrick

----------

Patrick Born Mon, 08/31/2009 - 08:38

Hi Edwin & Community,

Per product management, I've assigned both your CID and the CID issue defined at https://www.myciscocommunity.com/message/12637#12637 to CDETS# CSCtb67946

Engineering will now schedule a fix for this.

Next steps [very loosely described by me]:

1. Engineering management assigns task to Engineer

2. After analysis, a schedule is defined

3. Test code is produced

4. Code is tested by customer/s to verify fix

5. Code is tested, including regression testing

6. Schedule for general availability is defined

Regards,

Patrick

----------

Patrick Born Thu, 10/01/2009 - 14:55

Hi Edwin,

I've just checked on the CDETS. There is no progress information documented.

I inserted a note to bump the issue.

Regards,

Patrick

----------

the cid detection was fixed in the latest firmware but then it messed up other things regarding cid name field where its not escaped or encapsulated in quotes and causing calls to fail when pstn to voip gateway is setup with pstn cid for voip cid enabled. In the device config there is one field that says escape contact but that does it to the contact address, not the from field which is still broken, plus the device doesnt have any option to override cid name and/or number.

 

in syslog the deivce gives TP parse error:32 and below is the cid detection

 

FXO:Start CNDD
caller id parse number=065619999
fxo cnddwrap_feed parse ok 065619999  status=2
-- Caller ID:
--     Name             = ]▲╨
--     Remote Number    = 065619999
--     Dialable Number  = (null)
--     No Number Reason = (null)
--     No Name Reason   = (null)
--     Message Waiting  = (null)
--     Date and Time    = 05/11 12:06
FXO:CNDD name=]▲╨, number=065619999
FXO:Stop CNDD
FXO:CNDD Name=]▲╨ Phone=065619999
System started: [email protected], reboot reason:H0
System started: [email protected], reboot reason:H0
        subnet mask:    255.255.255.0
        gateway ip:     192.168.0.1
        dns servers(1): 192.168.0.1

EdGarritsen Mon, 11/23/2009 - 10:59

Cisco,

Any progress in solving this problem. I'm losing hope that I will ever get Caller ID working on my device.

Regards,

Edwin.

Patrick Born Thu, 12/03/2009 - 14:58

Hi Edwin,

The product management team are putting a list of modifications together in order to schedule Engineering resources to correct the CID problems on this device.

I don't have a schedule date available, but will remind Product Management that this issue is important to you and many other customers.

Regards,

Patrick

-----------

deeleins1 Thu, 01/10/2013 - 15:13

For anyone reading this (oldish!) thread - the latest firmware update sorted it for me... I had the 3xx version now have 5.2.13

Caller id works pstn 100% now (Germany) - couldnt get it to work with old firmware- (only worked voip)

btw- I  needed to use the tftp update method - could get the exe file to work.- failed to connect.(Windows7 ult - tplink tlwr1043nd (ddwrt))

Thanks Patrick for getting this sorted.

rgds Egg

antonical Sat, 05/04/2013 - 06:32

I only wish that were the case in the UK. I cannot get Caller ID  working. That last PSTN caller is not shown on the spa3102  web/admin/voice/advanced page internally the last pstn called number is  shown.

The last previous firmware was 3.3.6 currently the spa3102 has 

Product Information
Product Name:SPA-3102Serial Number:FMxxxxxxxxx
Software Version:5.2.13(GW002)Hardware Version:1.4.5(a)
MAC Address:xxxxxxxxxxxxxClient Certificate:Installed
Customization:Open

I  can post any config needed if someone can assist me with this. I have  read about everything I can find on the web over the last few weeks and  cannot find an answer to this.

I MUST STRESS THAT I AM IN THE UK so US or other solutions do not work!

Any help or assistance appreciated.

Best regards

Anthony

Actions

This Discussion