XO Sonus switch T1/PRI Outbound Problem

[tdaugirdas]

Has anyone successfully set up T1/PRI service using XO as the Service Provider. They are using a Sonus switch? They claim to be emulating 5ESS, AT&T Custom. Inbound works fine, outbound gets no D channel on local or long distance - just a wave-off. PRI is setup standard for 5ESS. No errors show up, no red light on DS1. ANY help would be appreciated.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[merlinman]

I did an XO PRI back in February. It was a very difficult cut.

Also, are you saying no "D" channel? That should keep inbound from working as well.

Rather than asking them for custom, ask if it's set for NI1, or NI2.

Legend/Magix like NI1, that's what custom is supposed to be.

Good Luck!

 

[tdaugirdas]

They claim only two available settings from their Sonus/Broadworks switch: DMS100 (which supposidly is NI-1) and 5ESS (which is supposidly AT&T Custom).

We will retry at the DMS100 setting and see what happens.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[ttech]

I never got it to work out here in PA. They ended up moving the circuit to a REAL 5e

It's been a while but i believe th D channel would crash when trying to dial out. Dialing in was OK

I got alot of use out of MONITOR that day

 

[ttech]

I remembered -- My situation was USLec with a SanteraOne softswitch. But I had the same symptoms.

 

[phonesrus]

I had an AT&T "WinBack" cut today on a DMS-100 with national NI2 with exactly the same symptoms, in ok, out wave off. This was on a Definity, but let me continue. When I got them to put a protocol analyzer on the circuit. What we found was that the calls out were being coded in ARS as "local" ie: 7 digit calls as opposed to "fnpa" or "hnpa" 10 digit calls, which is what they were supposed to be. We recoded the ARS tables and the issue went away, and heck it only took 3 hours longer than it should have.
Now!!
I ran across a Magic switch a while back with a PRI from one of the "oddball" CLEC's, My habit is to print some configs on my laptop for future reference, on their PRI print I noticed, later, that under Network Services instead of being coded as 56/64 digital data it was "virtual private network" which the manual says is DMS-100 carrier service for Magic to Magic connection.
Some of these new "CO" switches poping up are being built by data people, who tend to do things "funny", not telephone people.
I am throwing this out for you as food for thought. I think your issue, Tom, is a local vs national coding with the Sonus switch. I do not know if you are in a 7 or 10 digit area . Unfortunately the Legend/Magic does not have the granularity in programming that the Definity does.
I have done XO cuts to both Magic and Definity, but I have not seen your issue until today, but I can blame mine on the apparent idiot that installed it in the first place, everything was coded "local" except 011 "Intl" (which worked by the way) We had one heck of a "bridge" conference on mine for a while.

 

[SYQUEST]

Ya, those "data people" are "funny" alright.

Cisco thinks they invented telephony, and MicroStupid thinks they invented the computer!

....JIM....

 

[tdaugirdas]

Hi Guys - thanks for all of the input! XO tells me that they want no digits deleted for National, Local or International - so my Delete Digits table is all set to zeroes (which would be the standard setup anyway). Whether the customer tries to dial 7 digits, 10 digits and/or precedes the calls with a 1 - seems to make no difference. On outbound calls the Legend switch does not seem to be finding the D channel. I did try a change to their DMS100 switch emulation (which they say is NI-1)- but the results were the same. No problems with inbound DID calls - but no joy on outbound calls.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[phonesrus]

Tom,
You need to get XO to setup a protocol analyzer on the "D" channel and see what the outbound setup messaging says. The progress messages will show what is happening to the call and why you are getting a "reject" and what the "cause code" is.
The "D" is up and is working, as you say, because of the inbound calls. So the issue is why XO doesn't like what you are sending. It is not an issue of the number of Digits you are sending, the issue is the "type of number"-"TON" ie: "Local"-"National"-"Int'l" in the setup message that they are having "issues" with and is causing the calls to fail.
Exactly the same issue that I was having.

 

[kwing112000]

Every time i have had this issue where we could only get one way it was the wrong set up on the provider side. Like they are NI2 and tell me it is NI1 or custom. I would try to get one of their techs onsite and have him show you his Tbird when it is up on the line. what they can do is plug it in and hit auto. The tbird should auto set on the line and find what it is set to. I used to see alot of XO Pri out there in the notheast and we had so many issues with the techs in the noc telling us the wrong info. then they would ask you to reboot your end and you hear them typing and all of a sudden it comes up. With out a reboot. Then they say what did you do......

 

[tdaugirdas]

Phonesurus: They had a tech on site Friday - and of course -he could make calls in/out with no problem directly from the Cisco router on site. Not sure if he brought a TBird.

When XO monitored outbound calls (from their switch) - they claimed they could see nothing happening from their end.

As to "Type of Number" - they asked if the Legend could change that setting - I said no (unless there are some setting in PRI I don't know about).

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[TouchToneTommy]

Have you given an extension pool dial out code access to the PRI trunks - then dial the pool code instead of 9, and try placing calls? At least that will bypass tables, and let you dial directly on the trunk for testing.

 

[phonesrus]

Tom,
The Cisco router is a packet based switch, but it has an internal "D" channel trace capability that is pretty good, considering. It does absolutely depend on the abilities of the tech you are working with.
Have them trace an inbound call and tell you what they see, then immediately make an outbound call and see if they see the trace, they should if they are doing it correctly.
If you can't get this from them, then insist they hand you over to their next higher support tier.
They are going to have to make this work on what you are sending, pure and simple.
The "D" channel activity from setup to reject takes place in a second or less under "normal" conditions.

 

[merlinman]

phonesrus, do you know how to do this?

Is it something that can be done with a Either Net connection?

Does it require special software.

Let's just say, now you have my attention.....

 

[phonesrus]

Jack,
I have a limited knowledge of how to do it, because I have worked with Cisco techs and watched them do it, and I work with them remotely all the time, and I have a pretty good understanding of how it works. I think I mentioned in the past that I handle PBX's on large offshore drilling rigs. We do Packet based (Eithernet)connections to the rigs, voice and data, the voice is dropped to a T-1 or analog interface on the router (depending)and then into the PBX.
IP/Eithernet voice communications works just like the Internet. Basically it works like sending a letter, You have a receptient address and a sender address on the envelope (packet), You hand that off, it goes to a distribution center (router), it is then loaded on a carrier (internet- Satelite,etc.)then sent to another distribution center (far-end router),delivered to the receptient (T-1 interface), which then opens/reads the letter, acts on the information contained,ie: causes a phone to ring! Everything is contained in the packets!
Cisco routers are accessed via telnet over IP remotely, or a craft interface locally( all password protected, of course).
The interface is like using the old MS-DOS, Unix, or Linux, or in your case "Monitor". You have to know the command structure like "show Interface" and then be able to understand and act upon what you see.
The testing capabilities are in the software of the router, you just need a tech that understands it, and knows how to use it. Same for Programming, too!
It is not something you could could learn in a "Cisco for Dummies" or "Legend/Magic for Dummies" book (if there were any).
Now, you must excuse me, I have to get up at 3 am. to catch a bird to go 150 miles out in the Gulf, A Legend Processor died today, and I have to go perform CPR.

 

[merlinman]

OK, I will get more details from you later.

As far as a LEGEND/MAGIX FOR DUMMIES, I'm working on something, but it won't be for DUMMIES, 'cause it takes more than a DUMMY to work on these things.

Also, instead of a bird, I recommend an Airplane or a Helicopter, I'm not sure we have any birds big enough any more.

 

[memphisribs]

Tom, I agree with Phonesrus, you can change the type of call sent.
Example:
Special Service Table

Entry Number: 0 1 2 3 4 5 6 7
Pattern to Match: 011 010 01 00 0 1
Operator: none none none none none none none none
Type of Number: N I I N N N N N
Digits to Delete: 0 0 0 0 0 0 0 0


You may also, Verify that the Magix TEI is set for 0 ( Lines/Trunks>PRI>Protocol>TEI.)

Vendor should be able to look at the D channel with the proper tool and see why they are rejecting the call.

Hope this helps


42 years in the business and counting.

 

[tdaugirdas]

memphisribs: are you saying that is how the Special Service table should be setup??

The way I have it set is - everything at default: and under Outgoing Table>Special Service>Delete Digit - all the entries for the tables are set at zero.

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[memphisribs]

Tom,
I was saying that you set the type of number under Outgoing Table>Special Service>Typeofnumber to either National or International, dependant on what the carrier wants to see. Expect similar to my example for a LEC or CLEC. I always compare a working PRI print against my problem and look for differences. I also check the TEI setting under Protocol just in case.

Good Luck

42 years in the business and counting.

 

[tdaugirdas]

I'm EMBARASSED!! I did get the system up & running today with the existing XO switch and the Legend programmed in the standard way for 5ESS. I decided to do a triple check of the programming - and paid especial attention to CBC Service Patterns. I discovered that my previous user (who I was talking through the programming process via WinSPM - did not key in any digits after Pattern 0 (and this was the 2nd time reprogramming the system from scratch).. I guess I did learn something - you have to be VERY careful when walking an end user through the programming steps - especially when you cannot see what buttons he is actually pushing!! Unfortunately - I could not do the programming myself - because there was no way to connect to the system remotely (no analog lines available to dial-in).

Tom Daugirdas,
President
STCG, Inc.
stcg.com