Having trouble locating voice line on VG224 in order to TS it.

[Mogwai]

Hello, I've got a voice line I'm attempting to troubleshoot & reroute, but having trouble locating it. I was able to logically find it as coming from a VG224 due to the description on the port & it seems to be coming out of the large RJ-21 port on the front of the unit & then going to a 66-Block on the wall. The 66-Block isn't labeled very well. Is there any way to locate which wire pair the phone line in question would be on the 66-Block?  When I try testing the lines on that 66-Block with a butt set, I try calling my cell from the 66-Block lines & only get a greeting for Cisco Unity, but with no clarification the number for the tested line. 

[Maren Mahoney]

Someone else may have a more elegant solution, but one thing you could do is fire up RTMT and connect it to Unity Connection. There is a Port Monitor in RTMT that allows you to see incoming calls including the calling party. This should allow you to identify the lines as you dial from the butt set.

Maren        

[Jonathan Schulenberg]

Other options:

• If you know which pair is bad on the 66 block, just look at the RJ21 pinout in the install guide. Assuming they used a pre-terminated cable to the 66-block, the pinouts should match the pairs/rows on the block.
• Hop on the VG224 CLI and monitor which port goes off hook with your butt set

Either way, once you have the port you can look at the DN in CUCM under that gateway.

[Mogwai]

Thanks & sorry for the delay in replying, just got back to the desk after a small break. This does seem like it may be viable, but I'm not sure which pair on the 66-Block is the problem for option 1. 

As for option 2, how would that process work? From my limited understanding, I would be monitoring the live traffic of all the lines from the CLI (or RTLM)? and then disconnecting each pair one by one? If so, how would I be able to determine the 66-Block pair from that?

[Jonathan Schulenberg]

Connect your butt set to the 66-block pair you believe is correct based on the pinout I linked to and go off hook. You can verify that is the port using show commands on the VG224 CLI (e.g, FXSLS_WAIT_OFFHOOK vs. FXSLS_ONHOOK). If the VG224 is busy with a bunch of ports on active calls - and they rarely are these days - just repeat your test a few times to be sure.

[Mogwai]

Thanks for that clarification! I'll look into testing this out this week! Fingers crossed

[Roger Kallberg]

In the document Jonathan linked to there is a table that outlines the pairs in relation with the ports. With that information you can just connect your butt set to one port at a time in your panel and go trough each port and look in CLI which port that go off hook.

[Mogwai]

Thanks & sorry for the delay in replying From the RTLM, would I be monitoring Unity or Call Manager? From my understanding, it would be CM, since the number in question doesn't exist in Unity. When I do attempt to dial the number in question from my cell, it rings forever & doesn't appear in any of the  Session Trace Log View > Real Time Data logs that I can find.