Need help with H.323 trunk to Cisco CM 3

[mhshane]

Hello. Hope you are doing well.

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

Trying to connect to Cisco CM 9x
Located in Memphis, TN

AAR built
Route Pattern built
Trunk Group and Signal Group built

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

Can call from S8300 to Cisco; however, Cisco gets fast busy immediately when dialing the S8300. The moment you press the last digit it goes fast busy.

Cisco says it's a problem with the S8300 but I can't find the culprit.

From Cisco:
Here is what TAC has finally come back with on the issue. The setup is being sent to the PBX and the PBX responds with a release complete.

Thanks,
___________________________________
-Trace info back from TAC-

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 suggestions would be greatly appreciated.

Thank you.

 

[AvayaTier3]

You cannot direct dial TAC on h323 IP trunks between Avaya and Cisco
You can use AAR or uniform dialplan programming.

AAR Uniform Dialplan
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[mhshane]

Thank you for the info. Outbound is working via the AAR.
It is inbound from the Cisco that is failing.

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 for AAR
Then site code & extension

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

TRK 10 (TAC 510)
Sig 10

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


List trace shows proper setup and connection.



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 says the Avaya is giving it a "release complete".

Any ideas? Or is S8300, R014 too old to accept trunking with Cisco 9.12?

Thank you.

 

[janni78]

What do you see if you to a "list trace tac" on the CM when calling into the system?

"Trying is the first step to failure..." - Homer

 

[mhshane]

Nothing. No activity. Makes me more convinced Cisco isn't reaching the Avaya.
If the call is reaching the S8300 it is getting released by the Procr for some reason and never being passed to the trunk.
Could it be a bug? Maybe needs a patch?

 

[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

The Avaya doc shows it as blank

That was my missing needle in the haystack.

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.