E.164 alias question

[Xale]

Ok I'm new here so hiya and a newb to the VTC field, so with that in mind I'm going ask this question.

I have a system that is having a problem I have 40 or so tandbergs connected to an old Cisco 3520-GW being used as a Gatekeeper and I have Cisco 3542 MCU chassis with 1 MC06A installed. I'm running TMS 7 atm.

Now here is the funny thing, I can book a conference and if I book say 3 people they will all show up but the conference comes up as failed. But in the graphical monitor provided by TMS I can see all involved nodes as connected and I can see them on screen from the tandberg. But if I change the E.164 alias it works fine for about a day then I have to change the alias again to get it to work right.

I'm using pure IP there is no ISDN, so I'm curious is there something I need to turn on/off? Are there additional parameters I need to configure? this sytem was working just fine until about a week ago now it's just kinda funky. Any ideas (besides getting new equipment :paranoid: )? Like I said I'm pretty new to this so any help is greatly appreciated.

[Skylark]

The gatekeeper on the Cisco 3520-Gw is very limited and I have run into a lot of problems with it when I have tied setting in new products, specialy units that have an MCU capabilities built into them and whant to register two times.

If you telnet to the box when its not working can you see if its rejecting endpont registrations? If so look at the ports the endpoint are trying to register on and make a fixed registration on the gatekeeper using that port.

Easiest solution is to get a new gatekeeper to manage things (you could still use the old hardware).

[Xale]

Yeah the plan is to replace it on the next upgrade cycle for some reason this unit has been "overlooked" so it's been a real pita sometimes.

I will probably go ahead and permantely map the endpoints, I've already done it with the MCU and it seems to have stabilized.

Thanx for the input it is appreciated .