<!doctype Html

**burris** · 02-27-2009 02:00 PM

Originally Posted by bretski

The very reason I suggested *asking* about it.

One of the very first things the support team did (when I received a PAP2T) was upgrade me from 3.1.15 to 5.1.6. Their recommendation.

I could do this myself, but I'm still gun shy from having the original HT286 upgraded and then downgraded and then upgrading and downgrading on the HT502.
On my own SPA2102, I always upgraded it myself whenever new firmware appeared.

The PAP2T up was never suggested to me and I'm always reluctant to fool with a product that's not mine. Tweaking is one thing, but firmware is another.
Thanks for mentioning this. I will ask, although I can't imagine a box running any more reliably than this one....for me.

**sr98user** · 02-27-2009 02:03 PM

abward,
After the reboot, is incoming working for you?

**bretski** · 02-27-2009 02:16 PM

Originally Posted by burris

I could do this myself, but I'm still gun shy from having the original HT286 upgraded and then downgraded and then upgrading and downgrading on the HT502.
On my own SPA2102, I always upgraded it myself whenever new firmware appeared.

Totally understandable. I went through several up/downs on my HT502 as well.

Originally Posted by burris

The PAP2T up was never suggested to me and I'm always reluctant to fool with a product that's not mine. Tweaking is one thing, but firmware is another.
Thanks for mentioning this. I will ask, although I can't imagine a box running any more reliably than this one....for me.

No prob. After years in the tech industry, I'm with you on firmware upgrades. I'm a pretty firm believer in "if it ain't broke..."

OT, and FWIW: aside from my ongoing problem with CWCID, I am *very* pleased with the PAP2T.

**quattrohead** · 02-27-2009 02:29 PM

I just switched back to the HT286 because of HT502 issues inside my router.
I called support and got right through to James (i think) and he got me running again.
After a quick tweak of some settings to make them current and changing the port to 5080 so it stays well away from PP, everything is running smooth again.

The HT502 has its place on a simple network, but not in an "IT" type environment that most of us are running !!!!

**abward** · 02-27-2009 02:32 PM

Originally Posted by sr98user

abward,
After the reboot, is incoming working for you?

Yep, the phone rang just as I was reading your post. And, hold on to your hat, I was actually able to answer it.

So, I am rehersing:

Wife: Honey, what did you do today?
Me: Not much...

**fisamo** · 02-27-2009 02:35 PM

Abward--

To confirm, CallVantage uses the ports you posted for all of their devices, except the D-link DVG-1120M. If you have anything other than a huge gray brick for your CallVantage ATA (the 1120M--the model# is also on the upper right corner of the front panel), you're probably having a port conflict.

It sounds like Tim has switched your ports for you, so you should not have this issue any longer. FWIW, the 1120M is the ATA that I have from ATTCV, which is probably why I haven't had similar conflict issues between Voipo and ATTCV.

**abward** · 02-27-2009 02:39 PM

My CallVantage box is the Centillium MTA-1. So, sounds good.

Morals of the whole story:
1. If you have another ATA, make sure you tell VOIPo so they can port around it.
2. Make sure you check your router settings for ALG and SPI.

Maybe these should go into the FAQs.

**abward** · 03-02-2009 03:33 PM

Just got a call and the called id name was <null>, with an Unknown Number for the number.

**bretski** · 03-02-2009 06:01 PM

That's normal for some anonymous calls, and often from PBX systems. It see it quite a bit.

**abward** · 03-04-2009 07:16 AM

FYI,

I now have reason to believe that the port 5060 conflict may have been coming from a soft phone on my company PC. It uses Lotus Sametime Connect, and I just noticed that it talks on port 5060. It still could have been the CallVantage adapter, for all I know.