Call ID problem SOLVED

[rooster]

Hello All,

I'm wondering if anyone ever run across these problems with OBi100 and SPA-2102 on the same network.

Here are the following:

Linksys/SPA1001-3.1.19(SE)
OBIHAI/OBi100-1.3.0.2765
Linksys/SPA2102-5.2.13(004)

With the Sipura pap2 and the SPA2102 everything works flawless.

With the Linksys SPA2102 and OBi100 is where everything go wrong.

1. with the OBi100 and the SPA2102 together on the same network, all incomming call to the SPA2102 is showing the SPA2102's call ID randomly for the call ID.
2. with the OBi100 disconnected from the network, FPL is still showing on the SIP Status: connected with the SIP User Agent: OBIHAI/OBi100-1.3.0.2765
3. with the SPA1001 connected back to the network, with the same account as the OBi100, FPL is still showing that the OBi100 connection instead of the SPA1001.
4 . even without the OBi100 connected to the network, the call is still randomly showing the SPA2102's call ID ???

Update: The FPL Portal is now displaying as from 4. SIP Status: connected and the SIP User Agent: Linksys/SPA1001-3.1.19(SE)
Update 2: FPL is taking a very long time to update the SIP status.
Update 3: The call id issue seems to be my Panasonic KX-TG265B DECT 6.0 Digital Phone System caused the problem. It seems once I deleted all the phone book from the system, it's now working.

Edit: Change subject to Call ID problem SOLVED since it have nothing to do with any of the ATA's.

[rooster]

This problem might not be just be for the Panasonic KX-TG265B DECT, but might be for other phones as well.
If anyone experience this call display problem, I would strongly suggest you to clear out your phone book on your phone system before posting. This took me 2 days to figure out.

In my case, it just happens coincidentally for me to get a new ATA and was configuring at the same time the call display act up.

MOD: Please delete thread. Problem came back and Am out of ideas.