Two-way DID and T1 Assistance..

[GroundWire]

Greetings all..

I am trying to get a two-way DID T1 circuit working. I am able to make and take calls on the circuit, but the Magix R3 is confused by the digits being sent down from the CLEC - and it's constantly overflowing to the operator extension. (I get the "Cover DID#?" message)

The circuit is provisioned as TIE T1, ESF B8ZS, Wink/Wink, Tone/Tone.

The first NINE channels are live, and have I set them as "TIE", and the rest are "UNEQUIPPED". I've confirmed all nine channels are operational with the *03 trick.

My CLEC is sending me THREE digits, which exactly matches my dial plan (The DID's are xxx-1700, so they're absorbing 5, and adding a prefix of "1", which gets me my numbers).

I have even had them ABSORB ALL 7 DIGITS, and just SEND "101" all the time, I still get the "Cover DID#?" message on my operator console.

The circuit works 100% for sending and receiving calls, except for the fact the DNIS routing portion is not happening.

I am sitting in the CLEC's data center (about 200 feet from their switch), and their engineer has been working with me all day today trying to get this to work right.

What am I missing!? I'm going back tomorrow, and I'll be using monitor mode this time to debug the T1 circuit and confirm that I actually am being sent the digits that I require.

Thanks guys!

- Joel

 

[Pepperz]

The CLEC is not sending you what you are told. The "cover ? DID" on the operator phone shows that the digits sent with that particular call did not match the dial plan, so it goes to the operator. Since the CLEC will not believe you, you will have to set up a "test" phone and number it to match what you "think" they may be sending you. When the phone rings, then you will know what they are doing,.... then you can tell them what they are doing.

Pepperz@charter.net

 

[GroundWire]

The CLEC does believe me - I have no idea what they are sending, assuming it's not what it's supposed to be.

I'm literally standing over the shoulder of the guy as he's logged into their switch.

He is immediately changing how many digits he sends me in response to my requests for something different.

The CLEC is being amazingly helpful here, I am willing to accept there is a misconfiguration on the Magix still. Isn't that possible, or have I done everything I can with the rather limited way the Magix handles Two-way DID T1's.

- Joel

 

[Pepperz]

On a straight T-1, you have NO CONTROL over the digits you are sent. If 123 comes in, it goes to extension 123. It isn't the Magix. If your CLEC will cooperate, they can put a T-bird circuit analyzer or something similar, and monitor what they see.

Pepperz@charter.net

 

[GroundWire]

yup - I just got back from the CLEC.

We had a T-bird on it, and they are indeed sending me 101 down the pipe. The calls rings on the attendant console with the "Cover DID#?" message.

Let me confirm with you that all of these channels (all 9 of them) should be configured for TIE-PBX, correct?

I'm getting really irratated with this, because it seems like it should be working, but there's the one missing piece. Once I address this piece, then everything will continue to work the way it is supposed to... and everytime I "sell" this service to one of my customers, I will be able to make it work.

- Joel

 

[Pepperz]

I set them as tie-toll, but that shouldn't matter. Do you have an extension 101 in your system, ie., if you call 101 do you get a wave-off tone?

Pepperz@charter.net

 

[GroundWire]

no - It rings the phone sitting right next to me.

Tie-toll eh? ok, So what do I select when the next set of questions come up, somthing about Special Access or something like that..

- Joel

 

[Pepperz]

Once configured as tie-toll, set the channels, 1-9 in your case. The rest should should show U. When the calls come in, are they coming in on the expected channels? Double check that your channel / trunk numbering is accurate. When the tech is connected to the circuit, he should be able to see both sides of the circuit, and verify your settings, if they are in question. Is he checking at the PBX, or at the smart jack?

Pepperz@charter.net

 

[GroundWire]

805 is my first T1 trunk, and calls are coming in there every time as they should.

As I said earlier, I am sitting in the lab at the CLEC's office. There is an RJ-45 jack mounted on the wall, that is coming from their main phone switch which is on the other side of the wall.

His T-bird was connected between that, and my 100D module. There is no "smart jack" in this case, but that's certainly as close as I could get to one.

I'm not sure what he's verifying with the tester? I mean, the circuit WORKS - I can make and take calls, so obviously all of my signalling is correct.

The only thing NOT WORKING is the digits being sent down the pipe aren't triggering the typical routing behavior.

So I will try putting them in TIE-TOLL. Can you tell me please what distinction that makes please, so I can learn about whan you use certain things..

Thanks!

- Joel

 

[Pepperz]

From da book:
Outward and Toll Restrictions do not work with T1 lines emulating tie trunks when the lines are set to Tie-PBX or Tie Switched 56 Data. ARS or pool dial-out codes should be used instead.
Guess this can't be the problem. Might be time to start on the T-1 card. Go into maintenance on that slot, and see if there are errors. Might want to do a demand test on the board, and verify the CSU settings.
JOEL: I still tink it is the LEC, or at least upstream of the Magix. The digits are getting there, just not matching. Try this:
Say the number of the DID is 123-4567. Try renumbering a phone to 67, 567, 4567, 12, 123, 1234. My guess is that somewhere there will be a match. The fact that you had them all send 101, is unusual, so they may have given you something that doesn't match.
.......my money's on the CLEC..... still.

Pepperz@charter.net

 

[Ghostin]

I agree with Pepperz. Try changing the inbound signaling from wink to immediate and see if that makes a difference. Can they send the call down a particular channel or trunk. If so, you can monitor that trunk for the digits being received by using the monitor function.

 

[GroundWire]

I was able to change the inbound signalling to "auto", and at that point the calls were coming through, with NO digits. (The system acted like it normally would on a GS/LS card with on caller-id)

If I actually tried to change it to delayed, or immediate - I got an error beep.

The call IS coming down a particular trunk. Their switch is setup to send calls to channel 1-24, in that order. Since I am the only caller calling in, every time I call, I get the call on T1 channel 1 (trunk 805)... EVERY TIME.

As far as using monitor.. I can access it, but I've never seen any information (clear or cryptic) about how to use this tool for this particular task. Might you have any ideas? groundwire AT hotmail DOT C.O.M

I am going to try a different 100D card as well. I have to order it today, and it'll take three days to get here.. so.. :/

Thanks!

- Joel

 

[Pepperz]

Let's put this thng to bed. If the CLEC is willing to work with you, see if they can outpulse the specific digits of an extension near you. If that call goes to the operator as well, then then something is goofed. Are there any switches that act as relays between the CO and yoyr customer, that just may not be configured for the right signalling? It could be hardware, but , well, you know.

Pepperz@charter.net

 

[GroundWire]

Pepperz:

That is EXACTLY what's happening.. they can delete 7 digits, and send me "101", and it still goes to operator.

So yes, Something is goofed!

I also want to make sure you understand that I am not even onsite yet, we're testing this in the lab AT THE CLEC'S DATA CENTER. There is nothing between me, and their switch, except a sheetrock wall, and a faraday cage.

- Joel

 

[Ghostin]

who is the CLEC?

 

[Ghostin]

Another thing. Like Pepp suggested, instead of them sending 101, have them send 111. then renumber an extension 111, and 11. This will see if you or the system might only be getting the first two or last two digits.

 

[GroundWire]

hrm.. I never did mention that in this thread, sorry about that.

Advanced Telcom Group in Washington is the CLEC.

ahh - The way you said that made total sense, the way he said it, it made no sense at all.

I think we can arrange that.

Thanks!

- Joel

 

[Ghostin]

what type of equipment is the T-1 being provided by?

 

[GroundWire]

You know - I don't know what brand their switch is.. They use a whole boatload of Lucent stuff, but I can't confirm that's what is providing this circuit.

I'll have to ask them next week.

- Joel

 

[GroundWire]

The circuit has been delivered to the customer's physical location.

The CLEC is using a Lucent 5E switch. This is their "T-Fire" service offering, which means they bring in a full T1, and split it out using a Vina T1 integrator. Data comes out an ethernet jack on the integrator.

I'm also getting NINE channels out of the integrator, and plugging that directly into my phone system. We have CONFIRMED they are indeed sending the correct digits down the pipe - by having the CLEC's engineer plug their T-Bird directly into the SmartJack.

(the number block starts at xxx-1700, so they're deleting FIVE, and adding a prefix digit "1")

I have already tried a different 100D circuit pack.

I've tried configured the channels as Tie-TOLL, and it's no different than having them as TIE-PBX.

When I configure my "Incoming Signalling" as AUTO (just for testing), the system quits worrying about digits and just delivers the call like a typical copper line. Once I tell it to go back to WINK, it just covers to the operator extension, showing "DID#?" every time.

ok.. So I'm ready to actually pay someone to figure out what is going on here.

I wish I could get Merlinman's attention, just long enough to see if there is something I've missed.

Thanks..

- Joel