VoIP & CID (Caller ID)

**mikey** · 16-03-08, 02:43 PM

I have 2 VoIP ATA's.
1st is Linksys PAP2T, the second is a freshtel 3010 ATA.
I have 2 freshtel accounts with DID Numbers, the freshtel 3010 has inbound CID without problems, but with the PAP2T I can not for the life of me get it to work with CID.

I have tried all the things like swapping account info to the other ATA, swapping handsets to other ATA etc. Still no joy.

Anyone else have this problem with the linksys or know how to fix/setting to try?

thanks

**mal** · 16-03-08, 03:43 PM

Have you tried changing the ring cadence to greater than 2 seconds?

**best4less** · 16-03-08, 03:53 PM

Who are you with engin? ( I should read a bit better LOL)
I will send you a A PM Mate

**eyesee** · 30-03-08, 07:17 PM

... you will find that most ATA's are sipura originated (now linksys /cisco)

the devices you are using are sipura based and have capability to receive CID ...

The provider has already configured these devices with a provisioning script - which they can execute remotely when you 'register' to their network.

If they do and it works on one ATA - then it should be a setup issue only.

The device ID is known to the provider everytime you register - so you might find that the PAP2 could be barred from displaying CID (possibly part of subscription script)

I would check the firmware on your PAP2 and then do a H/W reset (total) and reconfigure from scratch ... you might have missed (or messed) something during your earlier reconfigs

16-03-08, 02:43 PM	#1 (permalink)
mikey Member iTrader: (0) Join Date: Jan 2008 Posts: 36 Spent time on board: 18:48:26	VoIP & CID (Caller ID) I have 2 VoIP ATA's. 1st is Linksys PAP2T, the second is a freshtel 3010 ATA. I have 2 freshtel accounts with DID Numbers, the freshtel 3010 has inbound CID without problems, but with the PAP2T I can not for the life of me get it to work with CID. I have tried all the things like swapping account info to the other ATA, swapping handsets to other ATA etc. Still no joy. Anyone else have this problem with the linksys or know how to fix/setting to try? thanks

16-03-08, 03:53 PM	#3 (permalink)
best4less I'am Not a Bloody Joke iTrader: (10) Join Date: Jan 2008 Location: Australia Posts: 2,618 Spent time on board: 1 Month, 4 Weeks, 0 Days and 11:49:21	Who are you with engin? ( I should read a bit better LOL) I will send you a A PM Mate __________________ Please wipe your feet before walking all over me

LinkBacks (?) LinkBack to this Thread: http://www.austech.info/voip/3370-voip-cid-caller-id.html
Posted By	For	Type	Date
VoIP on Austech.Info \| BoardReader	This thread	Refback	10-06-08 05:01 PM
VoIP & CID (Caller ID) on VoIP \| BoardReader	This thread	Refback	24-05-08 02:54 PM
"Ring cadence" - topic profile :: BoardReader	This thread	Refback	21-03-08 10:54 PM
Austech - Powered by vBulletin	This thread	Refback	18-03-08 08:39 AM

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

16-03-08, 03:43 PM	#2 (permalink)
mal Premium Member iTrader: (3) Join Date: Jan 2008 Posts: 227 Spent time on board: 2 Weeks, 2 Days and 17:59:44	Have you tried changing the ring cadence to greater than 2 seconds?

30-03-08, 07:17 PM	#4 (permalink)
eyesee Senior Member iTrader: (1) Join Date: Mar 2008 Posts: 141 Spent time on board: -	... you will find that most ATA's are sipura originated (now linksys /cisco) the devices you are using are sipura based and have capability to receive CID ... The provider has already configured these devices with a provisioning script - which they can execute remotely when you 'register' to their network. If they do and it works on one ATA - then it should be a setup issue only. The device ID is known to the provider everytime you register - so you might find that the PAP2 could be barred from displaying CID (possibly part of subscription script) I would check the firmware on your PAP2 and then do a H/W reset (total) and reconfigure from scratch ... you might have missed (or messed) something during your earlier reconfigs

Sponsored Links