×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Silly Lab CO Trunk Arrangement

Silly Lab CO Trunk Arrangement

Silly Lab CO Trunk Arrangement

(OP)
Since the Meridian 1's CO trunk do not support Caller ID, I am toying with feeding it inbound calls via a Cisco ISR. The ISR will ingest the Caller ID data and then forward the call, along with calling party info, to the Meridian over PRI.

This works great! However, I'd also like to leave the CO trunks directly connected to the Meridian so that outbound calls use them directly rather than going through the ISR.

Yes, this could possibly lead to issues with the system attempting to use a trunk that's already in use, but it's a lab environment and I'm OK with that (enabling dialtone detection might help if the analog trunk card I have will support it).

However, what I cannot figure out is how to configure the CO trunks in such a way that when a call comes in the system ignores the call. The Meridian will either 1) ring the defined ATDN on the route, or 2) ring the attendant DN which presumably is coming from NITE.

Is it possible to configure the trunk(s) so that inbound calls are ignored and not routed?

RE: Silly Lab CO Trunk Arrangement

Just send the inbound trunk to an analog phone port with no set connected to it and it will just ring and ring. Or to a Dummy ACD Que with no NCFW

RE: Silly Lab CO Trunk Arrangement

(OP)
KCFLHRC, I was thinking something like that. Was wondering/hoping there may be a more elegant solution, but that will work. big smile Thanks!

RE: Silly Lab CO Trunk Arrangement

(OP)
Ok, this works pretty well. The only issue seems that the M1 is sending ringback to the trunk. So depending on when the line is answered in relation to the ringback cycle on the M1, you may hear 1 to 1.5 worth of ringback. Is there a way to tell the M1 to not play ringback to the CO trunk?

RE: Silly Lab CO Trunk Arrangement

Is this configured analog phone or dummy acd? The ringback is more than likely not coming from the M1

RE: Silly Lab CO Trunk Arrangement

(OP)
At the moment I have it going to a SCN line appearance on a digital set. The ringback is most definitely coming from the Meridian.

RE: Silly Lab CO Trunk Arrangement

I hate to ask, but how do you know the ring back is coming from the M1 ? I'm guessing it's not

RE: Silly Lab CO Trunk Arrangement

(OP)
Because if I unplug the analog trunk, I don't get double ringback.

RE: Silly Lab CO Trunk Arrangement

(OP)
Basically what's happening is this...

Call comes in, the line goes through 1 ringing cycle so the ISR can collect Caller ID data. Once the ISR collects the Caller ID data, it then answers the line and PLAR's it to the MCR I have set up for said line. At that point, you get ringback from the M1 via the PRI (expected), but you *also* still get a 1 to 1.5 of a ringing cycle from the analog trunk.

I can reproduce this very consistently. Unplug the analog trunk from the M1, problem goes away.

There is a ring detection timer that I may play with.

RE: Silly Lab CO Trunk Arrangement

You may want to check the ring back fluid level in the M1, it may be overfilled. Kidding of course. Good luck with it.

RE: Silly Lab CO Trunk Arrangement

(OP)
I'm not exactly sure why it generates ringback on a loop start COT that it has not answered in the first place.

Here's a thread where they're experiencing the same issue: https://www.tek-tips.com/viewthread.cfm?qid=153906...

RE: Silly Lab CO Trunk Arrangement

(OP)
Looks like adjusting NRD under LD 16 seems to help. I bumped it down to the minimum (128 ms) and now no more double ringback. This "works", but was hoping for a more elegant hack (like disabling ringback tone on COTs configured a LOP). I'm sure in my experimentation I'll find a "gotchya" with this eventually. I think the solution is to source a loop start to ground start converter. big smile


NRD 128-(10112)-32640 - No Ringing Detector change

This timer monitors disconnect on unanswered or abandoned incoming CO/FX/WATS trunk calls. On loop start trunks this is the only monitor for such calls where as for ground start trunks, it serves as a back-up mecanism.

The timer should be set for four seconds longer than the ringing period which is normally six seconds. When the period (specified by the setting) expires, the timer will trigger a trunk disconnect sequence. Too small a default value can cause disconnects. To great a value can delay release of the trunk if the ringing has stopped.

On a ground start trunk, if the call goes on-hook, the 'NRD' is overridden by the 'ICF' timer, which has recognized a valid disconnect after the specified timer value has elapsed. The call is cancelled and not presented to the console.

On a loop start trunk, the 'NRD' timer is not overridden by the 'ICF' timer. The 'ICF' does not time since the loop start trunk does not give disconnect supervision. Therefore, the timeout period is the setting of the 'NRD' timer.

(Pulled from http://www.ghtrout.net/files/Early_LD16_NTP.zip)

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close