RING AGAIN

[coniglio]

I know what RING AGAIN is but the NTP is a little confusing. It describes RING AGAIN in relation to a busy DN and says if the DN is busy or ALL TRUNKS are busy you can activate RING AGAIN. I thought RING AGAIN was only applicable to internal (DN) calls but someone is telling me they're seeing RING AGAIN NOT AVAILABLE when making an external call. She doesn't have a RING AGAIN key but I didn't even think RING AGAIN could be used if you call an external number and that number is busy. Can you clarify for me please? thank you.

 

[ArchTelecom]

I beleive it refers to an all trunks busy condition. Not the other end being busy.

 

[coniglio]

the trunks on my end, right? although that's highly unlikely...they have plenty of T1 channels and also some backup POTS they can call out on. But assuming it does mean all my trunks are busy if I give this user a RING AGAIN key she'll be able to activate it and when a channel frees up she can do her thing? So I guess RING AGAIN is NOT only for internal calls, which I thought it was. thanks for the quick response.

 

[ArchTelecom]

If indeed the trunks are all busy in that trunk group and you have call back queuing enabled on the route data block, and if you use BARS/NARS, if all trunks in the trunk group are busy and the internal person dials a number outside, then the system will provide the option to use ring again (provided you have a RGA key defined on the set). When a trunk is freed up, it will be temporarily reserved for that person, the system will call the set with a special tone. They pick up the phone, press a DN key and the system will access the trunk and dial the number for them.

I'm bad with run-on sentences.

 

[coniglio]

So if we do NOT have call-back queueing enabled on the RDB would that cause her to see "ring again not available"?

 

[ArchTelecom]

That is probably the case, but I can not verify.
Maybe someone else in the forum can.

If you have a POTS to play with, create a RDB, put the POTS in the trk grp, enable CBQ, using an RLI route one obscure NPA or NXX through it for a few minutes and make a call, put it on hold and make a call with a second set....experience the feature. Then turn off CBQ and see what it does.

Don't forget to put everything back the way it was after the test.

 

[coniglio]

I think I figured it out. If the route (in LD 86) has CBQ NO (which in this case it does)the ring again option is not available and the display (I THINK) will say "ring again not available". The only part that still concerns me is that all the outbound trunks would have to be busy and that's hard to believe that could be the case but I guess it is. thanks for your help.

 

[ArchTelecom]

Correct.

Is it possible you have some defective trunks and the switch can not start them? Check all of your trunks for outbound calling manually via a maint set or using the call command in LD 36 to make sure they are all in good shape.

You may want to enable your traffic stats in LD 2 and have them report hourly. Look at your utilization and see how often all circuits are busy.

 

[mluckie1]

Have noticed this with PRI Trunks. Number called is busy and that feature is not available. See it once and awhile when calling a busy number.

 

[coniglio]

They have a T1. Thanks for all your help.