Search results for query: *

There's two parts to this answer. 1) IXCs will only transport tollfree traffic that "belongs" to them. All tollfree traffic your long distance provider receives from you MUST be on their network (i.e. routing to a switch/trunk group/POTS line YOU own in the US and have arranged with...

I'm an IXC providing PRI to a G3Si, three T-1s, one trunk group, NFAS. We support NorTel, Lucent 4E, Lucent 5E and System 85 protocol types (and they're pretty much generic).. we've got a customer who's reporting he's using a G3Si and he can't support anything but N449. We've turned up dozens...

The question is back to the HSDL pair...is there a controllable setting at the CO for echo? I've seen documentation that says there is but it doesn't describe how and the issues with ecans on the IXC network is moot - it doesn't matter if the loops are on DTC/DTCI shelfs with internal or...

yep, from everything everyone sees...but then again, if the local loop is unframed and the endpoints aren't (unframed), then the local carrier wouldn't exactly admit that either...it bears looking at closer though. I don't think we've been able to say HDSL loop D4/ESF framing issues have arisen...

Thanks Doc. The trouble is I'm an IXC using NorTel DMS-250s with SPMs and the only customers we have trouble with echo on are usually on customer-ordered loops, and those Loops are for plain jane T-1s for regular voice - and every one of those troubled customers are on a LEC HDSL loop. Usually...

anyone hear about echo cancellers on an HDSL T-1 used to carry voice traffic from Meridian PBX to DMS-250 (local loop using HSDL to the customer premise from the end office)? We're trying to figure out why echo is only occuring on T-1s that are HDSL provisioned by the LECs? Two ILECs carrying...

I'm showing the d-channel in service, back-up in standby and my LD carrier shows lockout on both, but calls are up...he's saying I need to turn crc-6 check to yes when talking to nortel SPMs,,,anyone offer advice?

My ld provider is saying they are set up to send me digits on an inband dtmf trunk with *ANI*DNIS*. Everytime I take a tollfree call from them, it goes to the auto attendant because the digits aren't right. I don't know if I'm set up that way *ANI*DNIS*...can anyone help..thanks

Thanks...the customer consulted his vendor directly instead of asking the LD carrier to fix it from their end...exactly as you stated, parms in the Definity weren't set...appreciate it!

Here's an example of the LD network settings...this is from a network DMS-250 that terminates on an SPM for a customer PRI group that's got two T-1s,using NFAs. (used to make 1+, terminate tollfree and can make VPN calls)...trunk group clli and default caller id have been deleted to protect the...

ooh..that's the kicker...we get some of the same questions only we work it in reverse (the long distance dms-250 usually is set up to match the customer switch)... If I've read the posts right, your options in the Definity are DMS-100 custom, DMS-250 and NI2, correct? If it's a local PRI, then...

Good afternoon...let me preface this by saying I'm not an Avaya person and I work in the Long distance world, primarily on Nortel DMS-250s...and I'm fairly certain that if your local or long distance carrier says they're sending ANISP on all calls, they are probably doing it. The trouble could...

I'm in the LD world, and from the IXC perspective, when dealing with our customers (either LECs or retail/wholesale), the idea is TELCO indicates the actual owner of the facility going to the customer premise, and CARRIER is the group who either ordered the circuit or where it eventually...

I'm enquiring from the Long Distance world. I've got a customer who has a Definity PRI terminating on a Nortel DMS-250. The trouble is when the customer is not providing the DMS with any calling party information element on the d-channel, we're not able to generate a calling party number to...

I'm not an Avaya expert or anything, but there could be a problem with the switch carrier your PRI terminates to...it could be the Intermachine trunks their network traverses doesn't have an ISDN transfer option enabled between their switches...I've seen it, and the end result is that caller id...