H.323 between Avaya and Cisco, Cisco calls fail, Avaya calls work 1

[mhshane]

Hello. Hope you are doing well.

Phone Gear Involved:
S8300, R014x.00.0.730.5
Located in Bogota, Colombia
IP Trunks available: 3

Trying to connect to Cisco CM 9.12
Located in Memphis, TN

Current situation:
From a Cisco phone I dial [#] [site code] [extension]
Example #1174 2580
And I get fast busy

From the Avaya I can call and connect without problem.
Dial [0] [site code] [extension]


Avaya programming:
Dial 0 to access AAR

Site codes are 11xx, 12xx, 14xx, 17xx, 18xx
So Disp AAR ANA shows:
11 8 8 95 aar
12 8 8 95 aar
14 8 8 95 aar
17 8 8 95 aar
18 8 8 95 aar


Runs thought Route Pattern 95
Inserting # because Cisco wants to see the dialed digits as something like #11554098

Trunk Group 10 (TAC 510)

Signal Group 10


List trace shows proper setup and connection. Real calls work fine.



What I can't figure out is why the Cisco can't complete a call.
I rings fast busy the instant I press the last digit of the string. That's too fast to have run down to Bogota and come back with "nope, sorry, don't like you"

And Cisco Technical Service says the Avaya is giving it a "release complete".

Have H.323 built to Memphis Sub, Memphis Pub and another Subscriber in Andover. Each H.323 trunk has one channel right now.

From Cisco Technical:
_
-Trace info back from TAC (Technical Assistance Center)-

We send the set up

60300003.000 |14:42:47.502 |SdlSig |H225Setup |wait |H225Handler(2,100,187,1) |H225Cdpc(2,100,189,125326) |2,100,13,1.1750795^*^* |*TraceFlagOverrode
60300003.001 |14:42:47.502 |AppInfo |value H323-UU-NonStdInfo ::=
60300003.002 |14:42:47.502 |AppInfo |{
callMgrParam
{
interclusterVersion 3,
enterpriseID ''H
},
supportedDtmfMethodParam
{
supportedDtmfMethod 3


but receive a release complete and that is why the Route list exhausted because there is no more members in the RL

60300010.000 |14:42:47.577 |SdlSig |SdlDataInd |wait |H225Handler(2,100,187,1) |SdlTCPConnection(2,100,13,37378170) |2,100,13,37378170.2^10.56.81.201^* |*TraceFlagOverrode
60300010.001 |14:42:47.577 |AppInfo |value H323-UserInformation ::=
60300010.002 |14:42:47.577 |AppInfo |{
h323-uu-pdu
{
h323-message-body releaseComplete :
{
protocolIdentifier { 0 0 8 2250 0 5 },
callIdentifier
{
guid '8046C4B17F22E6016C06574C46D80000'H
}
},
h245Tunneling FALSE


Any ideas? Or is S8300, R014 too old to accept trunking with Cisco 9.12?
Any suggestions would be greatly appreciated.

Thank you.

 

[whykap]

Age has nothing to do with this. H323 is a standard, as long as its supported by both platforms, and it is, you'll get it to work.
For starters, do you have MTP enabled on the cisco h323 trunk?
Also have you tried resetting the h323 trunk?

 

[mhshane]

I found the issue and it's not highlighted in the Avaya documentation.

For anyone who stumbles across this post in need of the documentation to configure H.323 between Avaya and Cisco:

https://www.devconnectprogram.com/fileMedia/download/bc78181f-1d03-41c0-9b52-32537dfe53be

Great document; however, there is one thing they missed highlighting

On the Signal Groups, make sure Trunk Group for Channel Selection has the proper Trunk Group number.
I'm using Trunk Group 95 for calls to my Cisco Subscriber therefore
Trunk Group for Channel Selection = 95

That was my missing needle in the haystack.

Thank you for responding with suggestions.
Cheers.

 

[mhshane]

I found one last wrinkle....calls sent to voicemail fail

List trace tac shows:
calling name and number properly
grabs trk grp 10 member 1
call-forwarding
term hunt-group 99
denial event 1751: No AAR/ARS route pat/pref D1=0x83000a D2=0x1c0019
call forwarding 68
term trk grp 10

Extensions have Cov Pa 99 -> Hunt grp 99 (ext 8299) -> Voicemail

List AAR Ana:
Dialed String[ ]Min[ ]Max[ ]Route Pat[ ]Call Type
[ ]8299[ ][ ][ ][ ][ ]4[ ][ ]4[ ][ ][ ]99[ ][ ][ ][ ]AAR

Any ideas? Thank you.

 

[thepfy]

What does Route Pattern 99 have configured on the S8300?

I would imagine the voicemail is connected via a trunk. Have you allowed trunk to trunk transfers between the Cisco H.323 link and the voicemail link.
It could be FRL related as well but it's been 6 years since I've worked on Avaya Red.

 

[mhshane]

I found the answer...and it's rather humorous.

I finally reached the phone guy on site at Bogota and he said they don't use voicemail. Said all calls route to the receptionist.

Well, 70% of the users have hu 99 as the first point of their coverage path so that isn't not correct.
And the other 30% had 3, 4 and 5 points for a total of 12 to 20 rings.
The users there just assumed the receptionist was receiving the calls and no one ever questioned it.

So now the local phone guy is going to get their vendor to get voicemail set up for each person and fix the bad coverage paths.

Mystery solved. Never would I have thought a system with a vm coverage path built and assigned would not be using vm.

Thank you for all the help. I appreciate it.