LINK between 2 sites

[bwtc]

I've got a strange one...

We have 2 active MICS. One on 6.1MR3, and one on 7.0.

We upgrated the one that is on 7.0 from 5.0 last night.

Everything seemed to have gone fairly smoothly.

There is one problem that we cannot figure ouot. Prior to the upgrade, we were able to remote page to the warehouse without any issues. But, for the past few weeks, the warehouse couldn't always page us.

When they would dial the dest code & then do a LINK, sometimes they would get dialtone & be able to continue, and other times, they'd get a quick dialtone, and then be disconnected. If I disabled the E&M card at the 5.0 location & re-enabled it, it would usually resolve the problem.

Prior to any of the systems being upgraded from 5.0, we never had any remote page issues.

Now that we have upgraded corporate to 7.0, the problem exists in both directions. If I dial the dest code to acces the warehouse & then press LINK, more often then not I'd hear a quick dial-tone, then be disconnected. Other times, the link would work.

We've checked the obvious stuff (remote access packages, etc), and since this problem happens on every channel of our tie lines (but sporatically), it most likely isn't a line / remote package issue.

I think it has to do with the link time, but do not want to start messing around with that unless I'm sure.

Any thoughts? And yes, our vendor is aware of the problem.

Thanks

 

[Phonehed]

Jumping from 5.0 to 7.0 is actually a pretty big leap from a system configuration standpoint. Many things will change as I recall, including routes and/or destination codes, target lines and possibly even some access codes if I'm not mistaken. I'd be looking at all of those things even if I did the upgrade exactly as recommended by Nortel.

Phonehed in Dallas

 

[bwtc]

Thanks, Phonehed...

I started doing some more research & think that I might have found what could be causing the problem.

The position of the Loop & T1 cards at our warehouse were swapped. This was initially done to allow outgoing calls to first be routed through our T1 back to corporate, and then overflow to a few copper lines.

We were trying to accomplish this with minimal system downtime (when the new T1 circuit was turned up). At the same time, we replaced the 6.1 with 6.1MR3.

We have since setup routes, overflow, etc to properly accomodate going over the T1 (pool B) with overflow to loop (pool A).

In playing with the link times, I discovered that when the positions of the 2 cards were swapped, the clocking wasn't changed to be primary on the DTI card (it is set to secondary). This is an invalid configuration.

Unfortunately, this will not be able to fix this until we are on-site, as the cards need to be disabled.

This is just a shot in the dark, as we do not have any voice issues going over the T1 (I would have thought that there would have been errors on the line).

Will advise once someone is on-site to perform this change.

 

[bwtc]

Update:

We have changed the ClockSrc on the T1 card at our remote facility to Primary.

This change still did not allow us to consistently page.

I restarted that system (Diagnostic Tools -> System Restart). Same deal.

I disabled & re-enabled the T1 card at corporate. Same deal.

Sometimes the Link works, other times, it doesn't.

So, from corporate, if I dial the dest code to the warehouse then do F71, probably 70% of the time, the call will drop. The other 30% will go through.

The numbers seem to be reversed going in the other direction.

As mentioned at the start of the thread, this did not exist when corporate was at 5.0 & the warehouse at 6.1 (non-MR). Upgrading the warehouse to 6.1MR3 caused the warehouse not to be able to page corporate consistently. Worked fine in the other direction.

Upgrading corporate from 5.0 to 7.0 caused the problem to exist in both directions.

Any other thoughts?

Thanks

 

[firenut1]

Bwtc, I would like to know how you programmed the both sites because i'am having the same issue.

Please let me know if you can help.