Added channels to new route ?

[skk391]

Hello All,

have a couple of questions.

I would like to configure a new route on my Nortel CS1000, then takes some TN (channels) from a exisiting route to place in my new route. Say if I put 18 channels into my new route would the customer hear a engaged tone after the 19 call?

 

[bignose21]

I you have a route with 18 channels in it and there is no alternate option in the RLI (LD 86) to route the call any where else when the route is full then the customer would hear the equipment busy tone (can sound like engaged tone, can be a long and a short tone, but can vary widely depending on country).

 

[skk391]

Thanks for this. This is what I am looking for. I need the route to give a busy tone when all channels are busy.

After reading a little I see that I need to

ld 16: create new route. where do I get the route number from, can this be any spare dn from the system.

ld 14- create trunks- the trunks are already built on another route. I have no idea of how to move the trunks from one route to another. Is this possible?

 

[sgorges]

After you have created your new route.
Go into the TN of the trunk through load 14 and changed the "RTMB" to the new route.
So if you built route 34 you would enter on the trunk TN


RTMB 34 1

Representing the first member of route 34.
The next TN would be

RTMB 34 2

Representing the second member of route 34

Hope this helps

 

[bignose21]

The route number is anything you want between 0-511 (large system 0-127 on a small) it just can't clash with an existing route. go in 21 and LTM the routes you will be able to see what route numbers are in use and the number of channels against them.

 

[johnpoole]

your using this just outbound? the 17th call will get all trunks busy (120 ipm) if you need to avoid that the step prompt in the rdb will step to another route... if you do that you can tgar users off of the second route are allow them access on a per station basis... om the rdb you can add several targ's, if that matches the tgar on the station it blocks

john poole
bellsouth business
columbia,sc

 

[skk391]

Hi all,

I wanted calls to come in to a route, and then when the route is busy it gives a engaged signal, so that 3rd party companies who are transferring calls to us stop doing so.

I thought that I could take calls from our route 0, add them into a new route.

How can I tell the system to accept calls from a 3 rd party company to come on this new route is this done through the IDC table?

 

[johnpoole]

no, you would have to get a new pri for that to work right. you can contact your vendor and have them block calls past the 16th channel.. that does not require a new rdb.. one way to do that is isa routes.. that sets a max inbound and max outbound..

we use that here but we never get a busy. the purpose here is to insure that if we have an external ie school bus wreck, all of our lines are not busy with inbound calls. at a hospital we need trunks in and out at all times

john poole
bellsouth business
columbia,sc

 

[johnpoole]

i assume you work at a gov site.. no one else would block inbound traffic. people with profit as the bottom line would add trunks and seats,

john poole
bellsouth business
columbia,sc

 

[skk391]

The reason is that we are passed calls from a third party and only pay for calls that we answer. If we cannot handle to call the 3 rd party would us to pass an engaged tone to their system so that they can then stop passing us calls and start passing calls to someone else.

Strange setup I know. We cant just have more seats because at the moment there is no structure to the way & time the calls are passed. In a single hour we could have 20 calls waiting and then have no calls waiting over the next two hours.

As usual I have taken the difficult approach in handling problem. We have symposium and have just discovered the 'GIVE BUSY' statement. so now I have use this when number of call waiting > 5 for something like that, without doing the call route setup this. However I would still like to practise setting up routes etc.