Problem with SPA3102 passing invalid caller ID names

[archie]

Unquoted CID violates SIP standard. We can not support such violation. You better bump Linksys to fix that bug.

 

[Bob Denny]

This problem is still present in the new 5.1.10(GW) firmware. Grrrrr...... I did bump Linksys/Sipura (I think!), and there are several posts on their forums about it. I'm a developer myself (astronomy observatory control systems), and occasionally I make accommodations for devices that come from reluctant manufacturers so I can have happy customers. I'm well aware that this sort of thing pollutes clean software. Plus it tends to remain in the code long after the original problem is fixed - future maintainers don't even know why its there unless it is commented thoroughly with a **HACK** marker or something.

But in this case, a very popular ATA is nearly useless for inbound PSTN calls in the US (cannot pass caller-ID). Please consider making an accommodation for this. It would be a matter of looking for the quotes, and if not there, adding them, then letting the rest of the code do its thing. Done right, it wouldn't be a risk for conforming SIP messages.

 

[archie]

Can you describe it algorithmically? Changes to ABNF?

 

[N_G]

We have an update to our template that should fix caller ID - it will be uploaded in the coming days

 

[MrKoen]

Not sure if this topic regards the same issue as I experienced last weekend, though as it might help someone out, I will share my solution. I experienced the problem where my to 3CX connected VOIP clients showed the internal number of the Linksys SPA3102, in my case 10001, instead of the number of the calling party. Googling on this problem I found multiple forums describing the same problems, most of them going into deeper changes and problem descriptions. I started playing with the SPA3102 settings a bit as I couldn't believe the problem to be that hard to solve and found out that the problem was indeed very easy resolvable by just setting a switch that wasn't mentioned in the SPA3102 tutorial on the 3CX website:

• Log into your Linksys SPA3102 using your webbrowser
• Go to PSTN line tab
• Look for the PSTN-To-VoIP Gateway Setup section
• Set the option PSTN CID For VoIP CID to yes
• Save your settings

Even though the status page on the SPA3102 shows the comma which most users experience as being a problem, it forwards the phone number correctly to the 3CX and thus to the attached VOIP clients.

 

[camoralesm]

We have an update to our template that should fix caller ID - it will be uploaded in the coming days

Hi Guys,

Does anyone know how to get access to that new template that "admin" mentioned it would be uploaded in back in 2009? I am testing this functionality with 3cx (v9-14507) and the SPA3102.. and the issue still exists. I do agree that the source of the problem is the SPA3102, since is passing a non-compliant "FROM" string.. however I think this can easily be handled by 3CX by making an exception..

For example.. if the FROM is supposed to be formated like (FirstName LastName, 5555555555) and when the display name has a comma, the SPA3102 passes (FirstName, LastName, 5555555555), which breaks makes the field invalid.. a way to resolve this.. would be.. to grab the whole string, identify the LAST comma (to check when the CALLERNAME is separated from the actual number), and treat everything before the comma as the CALLER DISPLAY NAME. That way, no matter what caracters are passed in the DISPLAY NAME, 3cx won't have issues with the formatting..

Again, I know this is workaround solution.. but since Cisco is dragging their feet on this... there should be other ways to get it working..

If the template announced by "admin" back in 2009, already resolves this, please let me know how to get it and install it. I checked the Gateway Templates list in the app updates section, and the one for the SPA3102 says "up-to-date" but it doesn't resolve the issue.

Thanks!