Paging busy tone

[adelainey]

I have three Nortel branch offices. If some one makes a page to the PA system and hangs up there is a 10 second delay before the user can do another page. They will get a busy tone.

This happens at 2 of the 3 sites. Configs look all the same across.

Any ideas where to start looking?

 

[KCFLHRC]

When I see people say the config is all the same I immediately question it. Different page controllers etc. Look at the route and trunk programming for each site and compare. I'm assuming this is some type of page controller, probably loop start trunk.

 

[adelainey]

I have looked over all route and trunk programming for each site and the only difference is the node ID. Other than that there is no difference. All hardware is the same as well. If you compare the chassis from one site to another, they are identical. Hence why I am not sure where else to look at why this could be happening. Is there a timing setting? I check the media card and doing a vgwShow, I see that the channel release the line as soon as you hang up after paging. I am not even sure what is providing the busy tone.

 

[StanleySteamer]

TRAC both the TNs in LD 80 while hearing the busy.

 

[KCFLHRC]

My guess is it is a disconnect supervision issue. Possibly on the page controller or in programming. Page control units don't send the disconnect signal like the CO does on a loop start trunk. Are the trunks build COT, WAT or what?

 

[adelainey]

Paging trunk is built as a WAT

 

[KCFLHRC]

It could be something as simple as a Tip and ring reversal causing the issue. But my guess is something may be a little off in programming. How about checking the SPCT prompt in the route as well as MANO in the route. Do a stare and compare to the one that works.

 

[adelainey]

SPCT and MANO are the same. How could I check for a tip and ring reversal?

 

[KCFLHRC]

Tip and Ring reversal would be at the terminal block. Try reversing the pair and see if that helps.

 

[adelainey]

Tried reversing the pairs and no such luck....

 

[adelainey]

Stanly, you mentioned to TRAC both TN's. Which 2 TN's do you mean?

 

[jaxuser]

what about the NEDC FEDC in your route data blocks - do they match?

 

[StanleySteamer]

When you are getting the busy signal TRAC the TN of set you are dialing from. You may get a clue from the MAIN_PM or TERM.
You could also TRAC the paging trunk TN immediately after a successful page to see if it is staying busy because of the paging equipment.
Are you having this problem when dialing the paging access code directly or are you dialing through a tie line first?

 

[adelainey]

I can check on the main and secondary cs1000's. They both are ETH Can that be looked up on the branch cs1000's? When I putty to them, they are just the base manager and ld's cannot be ran. Hope that makes sense....

 

[StanleySteamer]

Something else to check is whether the signaling pair is connected on the trunk TN. Some paging systems require signaling contacts from the CS1000 to activate the paging. That would be on the second pair of the trunk TN that is normally not connected but still has a purpose. I only remember this working as a signal from the PBX to the paging equipment but maybe it works both ways. Just a thought.

 

[adelainey]

Stanley,

I tried to TRAC the paging trunk TN but i get an error code. TN is 002 0 02 00

I think both... dialing 4 the *11 is how users do it on site. And i can dial 123 0408# to access paging remotely. 0408 is the access code. 8 is the node id for the site.

Hoping this is correct....

 

[StanleySteamer]

You say the trunk tn is 002 0 02 00 but the screenshot shows it as 000 0 02 00.

 

[adelainey]

Sorry. Typo

 

[StanleySteamer]

So what is the error code?

 

[adelainey]

All it will say is .TRA101