spa3102 & CID

Unanswered Question
Apr 28th, 2009
User Badges:

Hi,


I have configured my SPA3102 to handle CID on PSTN line. In our country the standard is ETSI FSK + V23. Everything is working fine - during a few calls or on first day. After that the 'Private caller' string is displayed on the phone, no caller id displayed on WEB information screen. If I switch off and on the device (SPA3102), the CID is displayed again during a few calls.

I use the latest firmware (5.1.10).


I hope, someone can help me.


Regards, kabelnet (Tamás Borlay)

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (1 ratings)
Loading.
Patrick Born Tue, 04/28/2009 - 13:27
User Badges:
  • Cisco Employee,

Hi Tamás,


This is an interesting problem. Do you have another SPA3102 that works all of the time?

Did this SPA3102 display caller id properly before you upgraded its firmware?


Regards,



Patrick

----------

kabelnet2 Tue, 04/28/2009 - 13:46
User Badges:

HI,

No, I have only one SPA3102. PSTN - Voip - Panasonic phone. Before that I used two phones - one with PAP2, other on PSTN.


There was the same problem before upgrade. I read somewhere on Internet, that the solution (to display CID) maybe the upgrade. I think it is not true, I changed the service subscriptions when the CID started to work. I was happy, but next day I get the 'Private caller' again. Then I found the 'reset technic' to restore the normal operation of service - but it is not comfortable. I want to found any solution. It seams, that there is problem only with CID, inbound and outbound is working fine, in both direction, without reset.


But it is not easy to get support in Hungary... I get the address of this forum from cisco.hu.


Regards, Tamás

Patrick Born Tue, 04/28/2009 - 15:08
User Badges:
  • Cisco Employee,

Hi Tamás,


Please do the following:

1. capture a syslog trace when caller id is working

2. capture a syslog trace when caller id is not working

3. save the SPA3102's configuration

4. send the two traces and the configuration to me at paborn at cisco.com


Regards,



Patrick

-----------

kabelnet2 Tue, 04/28/2009 - 22:08
User Badges:

Hi Patric,


Should I register as Cisco partner to download syslog server, or there is any other way to get that program? Because I am not and will not Cisco partner....


Tamás

Patrick Born Wed, 04/29/2009 - 08:21
User Badges:
  • Cisco Employee,

Hi Tamás,


You can do any of the following:

  1. Contact me at paborn at cisco.com and I'll send you slogsrv.exe for use on a PC
  2. Use a free syslog utility available from the Internet
  3. Use the syslog daemon available on any UNIX / LINUX computer


Regards,



Patrick

-----------

kabelnet2 Wed, 04/29/2009 - 09:40
User Badges:

Hi Patrick,


At the moment trace started there was no CID on phone. I called the SPA3102 with my mobil. The trace is trace_no_CID.txt, the status page is Linksys_SPA_Configuration_no_CID.html.


I switched off/on the device. I called it again with my mobil. The CID is displayed on phone. The trace is trace_OK.txt, the status page is Linksys_SPA_Configuration_OK.html.


I get the TP Parser error: 34 message during the trace, but it seams the server was working.


The difference, in case error:

FXO:Start CNDD
Calling:[email protected]:5060
[1:0]AUD ALLOC CALL (port=16408)
[1:0]RTP Rx Up
[0:0]AUD ALLOC CALL (port=16410)
[0:0]RTP Rx Up
CC:Ringback
[1:0]RTP Rx Dn
AUD:Play PSTN Tone 9
IDBG:sc-0
IDBG:rs:12

AUD:Stop PSTN Tone

If OK:

FXO:Start CNDD
FXO:CNDD name=, number=06209370726
FXO:Stop CNDD
FXO:CNDD Name= Phone=06209370726

Calling:[email protected]:5060
[1:0]AUD ALLOC CALL (port=16444)
[1:0]RTP Rx Up
[0:0]AUD ALLOC CALL (port=16446)
[0:0]RTP Rx Up
CC:Ringback
[1:0]RTP Rx Dn
AUD:Play PSTN Tone 9
AUD:Stop PSTN Tone

Thats all. I hope you can say anything. Thank your help! Regards, Tamás

Attachment: 
kabelnet2 Thu, 04/30/2009 - 00:02
User Badges:

Hi Patrick,


I change the description of the problem. After switch off/on the CID is displayed. I make a call with my mobil. If I hook off the phone, make a talk, and hook on the phone, then after that the CID is not displayed anymore.


Attached documents:

I saved the configuration before the 1st call and after the 1st call. The trace contains the full trace of the 1st (good) call and the 2nd (no CID) call.


Regards, Tamás

Patrick Born Thu, 04/30/2009 - 15:03
User Badges:
  • Cisco Employee,

Hi Tamás,


Thanks for the information. You can send any additional to me at paborn at Cisco.com if you need.

I'll analyse the attachments and report back.


Regards,



Patrick

----------

i have bought my spa3102 around 2 years back and till date i havent been able to get callerid working on it in the UAE, i have asked this question in almost all forums, even directly to linksys and it seems no1 has the answer to it and so i let it go thinking its not compatible in UAE untill the time when one person reported hsi callerid was working ocassionally leaving the spa to the default settings of bellcore but for me it hasnt even showed once and i have tried almost all possible way to get it running but it just wont for some reason and the main issue is even linksys wont help on it to get it working.


by using callerid converters etc in between the line and the spa, then it starts to show caller id so basically the hardware doesnt have any fault but its just the callerid standard isnt compatible with the device or its just the ring pattern and the time when caller id is sent and that time the device wont detect it due to some mis config so i would really appreciate it if some1 could finally get it sorted out.

Patrick Born Thu, 05/07/2009 - 13:02
User Badges:
  • Cisco Employee,

Hi Bipin,


I'll check with my colleagues to determine if they've any suggestions for me to share with you.

Please send me your config so I can analyze for anomalies.


Regards,



Patrick

-----------

Patrick Born Fri, 05/08/2009 - 12:09
User Badges:
  • Cisco Employee,

Hi Bipin,


I checked with my colleagues and was informed that UAE uses the same regional settings as the UK.

I opened up the SPA9000 Setup Wizard's UK.xml file and compared to your config and see that they are significantly different.


Please try the following changes to see if your caller id performance improves:

Voice tab > Regional tab > Miscellaneous:

FXS Port Impedance: 270+750||150nF

FXS Port Input Gain: -3

FXS Output Gain:  -3

Caller ID Method: ETSI FSK With PR(UK)

Caller ID FSK Standard: v.23


Regards,



Patrick

-----------

i tried, doesnt work and i think the PSTN port impedance is 600 and the FXS port impedance doesnt matter much, the calelr id method and standard u told me, i tried it, doesnt work at all, actually i have tried any and every combination of the things in both the lists but it just doesnt work so i assumed mayb its just not compatible but all of my dialup modem detect it very easily.


i even tried getting a universal caller id converter and it used to convert from existing to DTMF which spa3102 could detect easily but it never told me what was the actual standard used in the PSTN which still remains a mystery.


r there any test tools to detect the caller id standard on the line using the modem or any other hardware?

Patrick Born Mon, 05/11/2009 - 15:06
User Badges:
  • Cisco Employee,

Hi Bipin,


The impedance is important for proper caller id decoding. Please contact the provider of your PSTN line and ask them what standard they follow when delivering caller id. Better yet, locate their technical resources on the Internet and locate the caller id specification. Once identified, the SPA3102 can be appropriately configured.


Regards,



Patrick

----------

the pstn line provider has the following info posted on their site


ETSI ES 201 235-3      
Access and terminals (AT) specification of Dual –Tone Multi Frequency (DTMF) Transmitters and receivers; Part 3 Receivers.


thats the only info available and the impedance is 600, the reason i say this is because i have read on voxilla by other users also.

although the pstn line providers site says DTMF but i contacted the company and they said they use FSK and thats the only info i got out of them and i also use a LG Nortel phone and on it it says caller id = FSK (Type 1) and it works perfectly fine with my line in decoding caller id.

mayb some1 more experienced in caller id standards can explain what exactly is the standard when a device says FSK type 1 compatible.

Patrick Born Tue, 05/12/2009 - 13:32
User Badges:
  • Cisco Employee,

Thanks for this information Bipin.


Regards,



Patrick

----------

Patrick Born Thu, 05/07/2009 - 12:59
User Badges:
  • Cisco Employee,

Hi Tamás,


Looking over your configuration, I see that Voice tab > PSTN Line tab > FXO Timer Values (sec) > PSTN Ring Thru Delay: 1

This setting is extremely short for the device to properly receive caller id.

Please change it to 5 and test a few times. If caller id shows every time, even after use, then reduce to 4 and test again, reducing until caller id fails.

Once caller id fails, change the setting to 1 second more than when it failed and all should be good.


Please test this and let me know.


Regards,



Patrick

-----------

kabelnet2 Fri, 05/08/2009 - 00:42
User Badges:

Hi Patrick,


It seams, that it has no effect to the problem. I tried several values (1-9) with and without switch off/on the device, but the result was the same as the original situation: after the reset the first received call was fine but the others resulted 'Private caller' only.

The Ring thru delay = 1 value was the original one, I did not change it during setup.


Regards, Tamás

Patrick Born Tue, 05/12/2009 - 13:05
User Badges:
  • Cisco Employee,

Hi Tamás,


Thanks for testing this for me.

I am out of ideas for now and have requested support from Engineering.


Do you have any way to verify that caller id is always presented on your PSTN line please? Perhaps connect an analog phone that can display caller id and make several calls and verify that caller id is always displayed.


Regards,



Patrick

----------

hi,


yes the caller id works everytime on my phone connected to the PSTN line, i use a LG Nortel phone as well as a Siemens Gigaset and my 3Com dialup modem also displays caller id everytime.


my PSTN provider is called Etisalat and i think they use telcordia servers for PSTN and they use FSK caller id standard and after lot of testing, the spa3102 doesnt show any sign of polarity reversal when sending caller id.


when the PSTN wire is connected to the FXO port then the voltage is shown as -49 which i dont think should be an issue as the spa works with negative voltage also. Please let me know if those tip ring voltage etc such settings affect it or no.



Regards,

Bipin

kabelnet2 Tue, 05/12/2009 - 13:21
User Badges:

Hi Patrick,


Before SPA3102 my Panasonic DECT phone was connected directly to PSTN. It displayed always the caller id (if it was enabled on the caller side). I assigned different sound to different callers, etc. And it was working.

Now it is working after a rest, to the end of first call. I suppose, that something is not restored to basic status, therefore next time the caller ID is missing.

I asked my telecom about CID. The answer was 'ETSI FSK with Ringing Pulse Altering Signal, V23'. The tone parameters were get from http://www.3amsystems.com/wireline/tone-search.htm .

I hope, there will be any solution.

Regards, Tamás

Patrick Born Tue, 05/12/2009 - 13:30
User Badges:
  • Cisco Employee,

Hi Tamás,


"Now it is working after a rest, to the end of first call. I suppose, that something is not restored to basic status, therefore next time the caller ID is missing."

Are you saying that your Panasonic DECT phone only displays caller id for the first call?


What country is the SPA3102 located in? Who is the PSTN provider please?


Regards,



Patrick

----------

kabelnet2 Tue, 05/12/2009 - 21:55
User Badges:

Hi Patrick,


Sorry, if I was not clear.

Panasonic displays the CID if it is connected directly to PSTN. Everytime.

It displays the CID only until the end of first call, if it is connected to SPA3102.

My country is Hungary, telecom is T-Home.


Regards, Tamás

Patrick Born Wed, 05/13/2009 - 07:49
User Badges:
  • Cisco Employee,

Hi Tamás,


Thanks for the clarification.

While analyzing your log files, Engineering noticed log entries indicating firmware versions 3.36 and 5.1.10.

Can you confirm:

  • Which version are you currently using?
  • Are you experiencing caller id issues with both versions of firmware?


Regards,



Patrick

-----------

kabelnet2 Wed, 05/13/2009 - 07:56
User Badges:

Hi Patrick,


The 3.36 was the original firmware with which I bought the device.

When I detected the CID problem, I downloaded and installed the latest available firmware. This was 5.1.10. The CID problem was detected in both versions.

Now I use 5.1.10.


Tamás

Patrick Born Wed, 05/13/2009 - 14:35
User Badges:
  • Cisco Employee,

Hi Tamás,


Thanks for the information.


I escalated the issue to Engineering and they feel that the caller id problems could be a result of conflicting configuration parameters.

Can you please try the following:

Save your SPA3102's configuration

Factory reset the SPA3102

Configure the least parameters in order to get the SPA3102 working

Make 5 inbound calls and verify that caller id works on both the SPA3102 and on an analog phone

Assuming that caller id is now received each time that information is displayed on an analog phone, make one change at a time and then test with 5 inbound calls, until you are done, or the SPA3102 stops receiving caller id.


Please let me know of your progress.


Regards,



Patrick

-----------

kabelnet2 Tue, 05/19/2009 - 00:44
User Badges:

Hi Patrick,


Today morning I made the 'big test':


1. Factory reset (73738), set WAN, LAN, allow remote management
2. I added Voip proxy and login. It registered successfully.
3. First test: 1st call: CID OK, 2nd call NO CID!!!!!


After that, I think no other test is needed. But I restored the original parameters step by step, and tested the CID after the steps.


4. Restored dial plan (it has no effect to incoming calls) and caller id method ETSK FSK, V23.
5. Reset, test (I started the syslog server now. Sorry.). The same problem: CID is displayed at the 1st call only.
6. Restored the line parameters (220+820/120nF), disconnect tone and other tones at regional settings.
7. Reset, test, same problem.
8. I restored the original configuration.


Any suggestion?


Regards, Tamás


(I attached the log of the test.)

Attachment: 
Patrick Born Tue, 05/19/2009 - 06:33
User Badges:
  • Cisco Employee,

Hi Tamás,


Thanks for testing so thoroughly. For completeness, can you please save the device's configuration again for me.

Once I have your configuration, I'll send the syslog and current configuration to Escalation Engineering to see if they have any suggestions.


Regards,



Patrick

----------

Patrick Born Tue, 05/19/2009 - 08:22
User Badges:
  • Cisco Employee,

Hi Tamás,


I understand, and thanks for humoring me. I like the config again because this way, any "accidental, unmentioned" changes don't go unnoticed. :-)


Some questions:

1. I see that no debug or syslog server is defined in the config. Did you make any other changes prior to sending me the config?

2. Please confirm, caller id works every time for inbound calls from ITSP?

3. Please confirm, caller id only works for the first time after reboot for inbound calls from PSTN?


I am looking through the log file that you sent. I want to easily compare the first call to the second call but find that the log is full of other information.
















The log file shows 5 successful looking caller id but I can't easily identify failed caller id instances:

  • line 71 at ~ April 29 18H21
  • line 127 at ~ April 30 08H42
  • line 238
  • line 344 at May 19 09H21
  • line 466


Can you give me a clean log file please? Produce the log as follows:

a. configure logging on the SPA3102 and save

b. remove the existing sylsog file, start the syslog server, and document the time, example 19H43

c. make one call from external phone. [this time caller id should work]
     Document time, number that called, and document what phone on SPA3102 displays.

d. make one call from the same external phone. [this time caller id should fail]
     Document time, number that called, and document what phone on SPA3102 displays.

e. stop the syslog server

f. send me the entire syslog file.


Regards,



Patrick

-----------

kabelnet2 Tue, 05/19/2009 - 09:27
User Badges:

Hi Patrick,


1. I think, there are sevaral way to restore a configuration. I duble click on the saved HTML and press Submit changes. This restores the parameters were in the saved configuration. And because there was no logging at the time of save, it is not set in currect config also. (I switch off the logging when I do not use it, because generally the syslog server is not running on my PC.)

2. Yes, if PSTN is connected directly to my Panasonic DECT - it always displays the CID (at least if I use my mobil phone which was used in the tests).

3. When I wrote 'Reset & test', that means that I switched off/on SPA, made a call with my mobil, off hook - on hook phone. In this tests, there was CID during ringing of the 1st call (call after reset), and there was not CID during other calls.


I prepare you a call with CID and without CID. In CID_is_OK file, in 2nd and 4th lines the number is the CID.


Regards, Tamás

Attachment: 
kabelnet2 Wed, 05/20/2009 - 04:20
User Badges:

Hi Patrick,


I made the test again to give you clear documents:

1. Factory reset, set WAN,LAN, remote management.

2. Set Voip proxy parameters - nothing else.

3. Start syslog on PC & SPA.

4. Save configuration (...before_1st_call)

5. Make a call from my mobil, CID is OK, displayed. Hook off, on.

6. Save configuration (...after_1st_call)

7. Make a call, NO CID (Private caller). Hooh off, on.

8. Save configutarion (...after _2nd_call)

End of test.


I hope this help you. Regards, Tamás

Patrick Born Wed, 05/20/2009 - 04:57
User Badges:
  • Cisco Employee,

Thanks Tamás,


I'll take a look and then escalate.


Regards,



Patrick

-----------

kabelnet2 Fri, 05/22/2009 - 00:42
User Badges:

Hi Patrick,


An additional information: the CID is displayed fine when the call is received from Voip line.

(It is a rare situation in my practice, but today I received such call and the CID was displayed.)


Regards, Tamás

Patrick Born Tue, 05/26/2009 - 14:00
User Badges:
  • Cisco Employee,

Hi Tamás,


Thanks for the additional information. I escalated last week to Quality Assurance and Escalation Engineering. They're not previously experienced the reported behavior. I'm hoping that they will have some thoughts on how best to troubleshoot this.


Regards,



Patrick

-----------

Patrick Born Thu, 05/28/2009 - 03:49
User Badges:
  • Cisco Employee,

Hi Tamás,


Can you please provide very a detailed, step-by-step description of how you configure the SPA3102?

Escalation Engineering have engaged and want to attempt to replicate the problem in Cisco's labs.

In order to do this, we need to know exactly how the device is connected and what changes you make after factory defaulting the device.


Regards,



Patrick

-----------

kabelnet2 Thu, 05/28/2009 - 07:08
User Badges:

Hi Patrick,


I have a home network with WRT610 and an ASUS Gigabit switch. The Internet is connected to WRT610, my computer and SPA are connected to teh switch. This network uses 192.168.0.x addresses. My PSTN line is connected directly to SPA, otherwise my Panasonic DECT phone is also connected directly to SPA.


After factory reset I connected my notebook to SPA and I changed its address to 192.168.1.1, and allowed remote control. I saved the changes. After that I could control the device from my computer using its address on that network (192.168.0.116, I use reserved IP). I reduced the private IP range to my network (192.168.x.x), but it is not interesting. During the test I set the syslog and debug server address (to my computer) and debug level to 3 also.


After that I continue the configuration from my computer (connected to WRT610). I set only the minimal to Voip service: SIP proxy require, proxy, user id and password. I saved the changes and start the test. During the second call the CID display problem occured (see the description of test).


This was the full description of the setting before the 1st test.


The full setup of SPA contains the followings also:

1. On Regional tab I set the CID method, the FXS port impedance, and call progress tones to Hungarian standard

2. On line1 I set dial plan

3. On PSTN line I set FXO port, disconnect time, and change the long silent parameters (there was automatic disconnect during long calls, therefore I changed the parameters).


Thats all. You can see the used parameters on the saved configurations sent before.


Regards, Tamás

Patrick Born Thu, 05/28/2009 - 13:08
User Badges:
  • Cisco Employee,

Thank Tamás,


I'll forward to the team for analysis.


Regards,



Patrick

-----------

kabelnet2 Fri, 05/29/2009 - 01:22
User Badges:

Hi Patrick,


I am sure, that I wrote somewhere in the past, that the CID is correctly displayed until the first Off hook - On hook action, and it is wrong after this sequence. I think it is important for your team, because it means, that SPA correctly detects the CID with original settings (=> settings after reset), but the Off hook - On hook sequence changes any internal status which causes problem in CID detection or processing.


I made a new log file about that. Reset, call-disconnect, call-disconnect, call-disconnect,call-off hook-on-hook,call-off hook... was the sequence. In first 4 cases (until the off hook)  the CID was correctly displayed during ringing. After off-hook-on-hook only 'private caller' was displayed.


Regards, Tamás

Attachment: 
Patrick Born Fri, 05/29/2009 - 04:16
User Badges:
  • Cisco Employee,

Hi Tamás,


Thanks for this new information. I'll share with the Test & Engineering teams that are attempting to replicate this issue.


Regards,



Patrick

-----------

Patrick Born Fri, 05/29/2009 - 15:10
User Badges:
  • Cisco Employee,

Hi Tamás,


Thanks to your patience, detailed explanations, config files, and logs, the Cisco team have been able to replicate the issue in our labs.

Now that the team can replicate the issue, they can work to understanding the root cause and work on developing a fix.


I'll keep you posted, but feel free to ask for a status at any time.


At this time, I do not yet have a time-to-fix estimate.


Regards,



Patrick

-----------

kabelnet2 Sat, 05/30/2009 - 05:25
User Badges:

HI Patrick,


This is a very good information. Thank your help. I am waiting to the solution.


Regards, Tamás

atkellyxx Mon, 07/13/2009 - 04:37
User Badges:

weeelll?


i have the exact same problem in Australia.


However I seem to recall that before my firmware upgrade i had CID working on both voip and pstn, now i only have voip cid coming through.


i am keen for a resolution on this.  thanks in advance


anthony

Patrick Born Mon, 07/13/2009 - 14:10
User Badges:
  • Cisco Employee,

Hi Anthony,


I'm checking with the team and will get back to you with an ETA for a fix.


Regards,



Patrick

----------

atkellyxx Mon, 07/13/2009 - 16:49
User Badges:

Thanks Patrick


That would be great.  Was trolling the net last night and have found a bunch of people on other forums reporting the same issue.  Some said they solved it but weren't specific how.


Looking forward to it.


Anthony

marwan-an Mon, 07/13/2009 - 21:31
User Badges:

Hi Patric,

I am having a comparable proble, please keep me posted of the availability of a fix.

I am living in Ontario, Canada, and my service provider is Bell. The symptoms I have are the following

1- PSTN call received

2- Phone rings, CID is displayed

3- If the phone is not answered after the 2nd ring (Same call), the CID switches to "Private Name, Private Number"


I am running firmware version "5.1.10(GW)" on my SPA-3102 with H/W version "1.4.5(a)".

Other phones in the house work just fine. The SPA does not have a record of the "Last PSTN Caller"

Regards,

Marwan

Patrick Born Thu, 07/16/2009 - 11:13
User Badges:
  • Cisco Employee,

Just to let you know that I am still making contact with the development team in order to get an ETA on a fix.


Regards,



Patrick

-----------

pdjackson Sun, 07/26/2009 - 12:27
User Badges:

Hi Patrick,


Any update on when we can expect a fix?


Thanks,

Peter J

Patrick Born Wed, 08/19/2009 - 07:38
User Badges:
  • Cisco Employee,

Hi Peter,


Apologies for the delayed response. I'm checking with product management and will report back shortly.


Regards,



Patrick

----------

Actions

This Discussion