They “fixed” it by changing the PRI format from standard to Public whatever that does on an Avaya. Wanted to post that so if anyone else runs into it the web searches will catch it.
From: [email protected] [mailto:[email protected]] On Behalf Of Brian Meade Sent: Thursday, December 04, 2014 4:22 PM To: Mike Cc: [email protected] Subject: Re: [cisco-voip] Avaya PRI to CUBE to Percipia I'm not super familiar with the gateways but I know I've got some gateway guys at Avaya that were able to do it straight from there. On Thu, Dec 4, 2014 at 3:42 PM, Mike <[email protected]> wrote: They are using list trace. Any other way to pull digits ? Sent from my iPhone On Dec 4, 2014, at 3:26 PM, Brian Meade <[email protected]> wrote: Where are the Avaya guys observing the 13 digits? A lot of them don't actually check it on the gateway and just rely on a "list trace" in CM and don't look on the actual gateway. On Thu, Dec 4, 2014 at 3:15 PM, Mike <[email protected]> wrote: Hey all I’m running into a problem where I can’t make international calls through an Avaya switch nor can I get DTMF from the Avaya, but 7,10 and 11 digit dialing works fine. DTMF from Percipia through the CUBE into Avaya works fine. Of course the Avaya guys are blaming Cisco, but I can see all 15 digits passing to the PRI to Avaya with a q931 debug. The Avaya engineers are only seeing 13 digits. I’ve changed the isdn type and plan from unknown to international and still no go. Has anyone ever seen this before? Thanks, Mike _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
