spa3102 TP parse error:32

bipin · ‎05-12-2015

spa3102 gives a TP parse error:32 in syslog when pstn cid to voip cid is enabled, it detects the cid from pstn but when sends the call to gateway on the internet or pbx it doesnt escape the from heater name field, it needs to send the cid name field within quotes, plus when it doesnt detect cid name from pstn but jsut number, it insert garbage characters in from field but contact header display fine and strips out garbage characters.

this issue has been since long on previous firmware updates as well including the latest firmware

syslog details below in image

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: ip@192.168.0.2, reboot reason:H0
System started: ip@192.168.0.2, reboot reason:H0
        subnet mask:    255.255.255.0
        gateway ip:     192.168.0.1
        dns servers(1): 192.168.0.1 - See more at: https://supportforums.cisco.com/discussion/10709471/spa-3102-caller-id-not-working#sthash.4Zs9dEtK.dpuf

bipin · ‎05-12-2015

not quoting the cid name violates the RFC standard causing the device to not work with many PBX and switches like asterisk, freeswitch etc

Dan Lukes · ‎05-23-2015

Cisco technicians doesn't read those threads. If you wish to report the firmware bug, call SMB Support Center. But don't wish for so fast solution.

bipin · ‎05-23-2015

i have already done that and the person on the other end asked me to send a picture of the device with the serial number which i did at espasov@cisco.com after which i have emailed him couple of times on the status which he didnt reply to and i believe he has closed the ticket even.

Its no point having a support department which doesnt work at all and asking for support or bug fixes is like begging them to do it which they still dont do for years.

atleast when u sell a product in the market make sure it works even properly, its like, the product has a bug and u want them to fix it but they will only listen to u when u pay them to do so and that too has no guarantee if it will ever be fixed in years.

the last caller id issue took 6 years to fix and that too others still complain about it as still not working perfectly

Dan Lukes · ‎05-24-2015

My experience is the same. There's no good customer support for SMB.

As Cisco SMB phones have some exceptional features not seen elsewhere, we are not going to use phones of other vendor here. But it apply to phones only. Other VoIP components are non-Cisco all the times.

Unfortunately, I can't recommend a good FXO<->SIP gateway to you. Our installations are done mostly in Europe - and FXO is rather rare here. And even if our customer have one, it's easy to convert it to ISDN-2. So sorry, I have no personal experience with SPA3102 nor I can recommend a good replacement for it.

amchang · ‎05-29-2015

Re posted to ATAs, Gateway and Accessories