Voxalot / SIP Broker Support Forums - View Single Post

boatman · 08-31-2007, 09:37 PM

Well, what I know is this;
-----
I can call other Voxalot users without problems.

The only affected calls are those that match some VSP in my Voxalot dial plan.

I can register my ATA directly with my VSP and the calls work even with Block CID Setting set to yes.

When call fails, it's the Voxalot lady voice message that says the call cannot be completed, Voxalot is not even passing the call to the VSP.

Dozens of VSPs can accept 'Block CID Setting' calls from thousands of SPA2102 units across the whole world, but Voxalot cannot.
-----
So it seems obvious it's an issue with Voxalot. It's as if Voxalot was detecting my ATA model, and if that matches SPA2102 then Voxalot require CID in order to send call to the VSP.

08-31-2007, 09:37 PM	#3
boatman Senior Member Join Date: Jul 2007 Location: Oregon, USA Posts: 365 Thanks: 17 Thanked 77 Times in 64 Posts	Well, what I know is this; ----- I can call other Voxalot users without problems. The only affected calls are those that match some VSP in my Voxalot dial plan. I can register my ATA directly with my VSP and the calls work even with Block CID Setting set to yes. When call fails, it's the Voxalot lady voice message that says the call cannot be completed, Voxalot is not even passing the call to the VSP. Dozens of VSPs can accept 'Block CID Setting' calls from thousands of SPA2102 units across the whole world, but Voxalot cannot. ----- So it seems obvious it's an issue with Voxalot. It's as if Voxalot was detecting my ATA model, and if that matches SPA2102 then Voxalot require CID in order to send call to the VSP.