Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Early cut through" configuration 1

Status
Not open for further replies.

blinking123

Technical User
May 10, 2004
45
US
Environment:
Magix R1.0 w/100 R INA, 800 DID, 016 T/R, 412 TDL

Local carrier and services:
Qwest OneFlex Integrated Access - a single T-1 circuit that transfers data, accesses Internet, carries all local, long distance as VoIP (up to 6 voice channels)- Cisco 1760 hands off voice traffic as PRI to Magix.

so here's the rub:
Outbound calls to certain toll free numbers fail to interact with IVRs- the DTMF tones we're trying to send aren't acknowledged (e.g., Delta works, American Express doesn't, AAA doesn't, FedEx does).

If the outbound call is placed over a POTS through the Magix, it works perfectly to all IVRs.

Qwest is telling us we've got to change the Magix programming to "early cut through on the D channel".

Our vendor says this isn't an option.

Qwest techs are saying in call traps to the failing IVRs they aren't seeing our DTMF tones - the Magix doesn't believe it's really connected to the IVR.

Vendor says it's not the Magix - classic PRI's don't have this issue, it's gotta be Qwest's config for VoIP that's goofed, or the Cisco is goofy...

Any ideas?

Thanks in advance~
Annie

 
I have never mesed with this, but I understand their may be something like what you are looking for under:

System Program > Start > Lines & Trunks > PRI > Protocol > Timers

Now you can see about 12 Timers that can be changed.

There may (or may not) be some type of timing issue connecting to these (NON-STANDARD) connections.

I would probably ask AVAYA if they had any insight to this issue.

I am assuming your VENDOR is the one doing the PROGRAMMING on the MAGIX.

If they are, and they are a real AVAYA Vendor, then they should have access to Avaya's TIER-3 Engineering group.




 
Thanks for the reply, Merlinman.
Yep, we looked at the sysprogramming hierarchy and saw those many options to which you refer... and our equip vendor is no longer Avaya certified ... and yes, we'll put in a request to Avaya directly ...

We all face this finger-pointing between carriers and equips - and while the concept presented by both sides makes sense, I'm leaning toward our equips explanation/reasoning "the Magix never had difficulty communicating on call answer issues with it's previous PRI's - PRI's that were configured by the carrier in typical fashion for PSTN solely."

So, if anyone out there has ever had to re-config protocol and timers due to this VoIP/PSTN stuff, figured one of you geniuses would've done it.

Thanks again!
Annie
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top