SPA232D doesn't send caller ID to line1 when pstn is off hook

jcharles608 · ‎11-11-2017

I have a SPA232D connected to the PSTN via its FXO port, and an analog phone connected to its Line 1 (FXS) port. Asterisk is on the network to handle routing calls between the SPA232D's ports, another SIP device and a Twilio SIP trunk.

I've found that the SPA232D is not sending Caller ID to Line 1 under this circumstance:

1) A call is in progress between the a SIP device and the SPA232D's PSTN port (doesn't matter if the PSTN call was inbound or outbound)

2) A new call is initiated from a SIP device to the SPA232D's Line 1 port.

This works just fine if the PSTN port on the SPA232D is on-hook/idle. It seems like the SPA232D can't send caller ID to its Line 1 port if its PSTN port is also off-hook. In both cases, I see the same INVITE info going from asterisk to the SPA232D, so I'm pretty sure the problem is not there.

The SPA232D is on firmware version 1.4.1, which is the newest shown on Cisco's download page.

Has anyone else encountered this?

Dan Lukes · ‎11-12-2017

It sounds like bug in SLIC driver. Unfortunately, SPA232D is End of Phone Support: HW already. Unless you have valid support contract you are out of luck. If you have support contract, call support center, but don't put so much hope on it. I consider Cisco's support of SMB segment rather poor.

There are two hardware versions of SPA232D - with the old SLIC chip (Device 2 & 3) and with the new one (Device 1). I'm just curious - which one you have (check serial number)?

SPA232D of other HW version that the one you have now may (or may not) work as expected. But it's not easy to buy device of particular HW version ...

jcharles608 · ‎11-13-2017

It's always fun to learn that a product you bought six months ago is now EOL. :-)

Looks like the solution may be to pick up something like a SPA112 and move the phones off to that, using the SPA232D just for the PSTN interface.

What's another $30 if I've already come this far, right? ;-)

Thanks for the info!

JC

Dan Lukes · ‎11-13-2017

It's always fun to learn that a product you bought six months ago is now EOL. :-)

If you bought it six months ago, you bough product that has been End-Of-Sale at the time of purchase and even more than year before it. Reconsider the seriousness of the supplier ...

End-of-Sale Date

The last date to order the product through Cisco point-of-sale mechanisms. The product is no longer for sale after this date.

December 19, 2015

pick up something like a SPA112 and move the phones off to that, using the SPA232D just for the PSTN interface.

Forget SPA112 and buy an native IP phone instead. Either something like SPA3xx (or SPA5xx), or a IP phone from other vendor. I have few SPA112 - it so often deliver no Caller ID to phone. I never analyzed the true cause - may be it's SPA112 fault (e.g. it's not sending CLID), may be it's just incompatibility between SPA112 and analog phones (several types) - but my conclusion is - it's not so reliable.

Well, I'm speaking of more than just another $30 here.

Just my $0.02 ...