[cisco-voip] Avaya and CCM 4.3 Integration over H323 Trunk
Humayun Sami/Engineering/Karachi
Humayun.Sami at wateen.com
Wed May 18 16:35:16 EDT 2011
Thanks Floh for all the time you spent here, I have read the same logs earlier on Cisco VLT (a stuff that tac uses), the information you mentioned is all good.
Avaya is not able to call us coz when they dial the trunk access code 811 to get a dial tone, when they don't get the dial tone or as they say our trunk they get a fast busy tone after 811, so they cant dial further. This is the main reason Avaya is not sending the dialed digits. The main reason is they don't get to reach the trunk.
Regards,
Humayun Sami.
________________________________
From: Florian Kroessbacher [mailto:florian.kroessbacher at gmail.com]
Sent: Thursday, May 19, 2011 12:08 AM
To: Humayun Sami/Engineering/Karachi
Cc: Bantz John F; Humayun Sami; <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Avaya and CCM 4.3 Integration over H323 Trunk
Hy,
i looked at the trace
Is this the Szenario you have tested:
1) Call Beginn:
Outbound H225 SETUP message to 10.95.3.210 at timestamp 05/17/2011 16:47:42.272
SETUP, pd = 8, callref = 0x0004, Message Size = 144 bytes
Bearer Capability i = 0x8090A2, ITU-T standard, Speech, Circuit mode, 64k, µ-law
Display i = 'Ali Raza'
Calling Party Number i = '5528' - Plan: Unknown, Type: Unknown, Presentation Allowed, User-provided, verified and passed
Called Party Number i = '3115' - Plan: Unknown, Type: Unknown
User-User, i =
2) I think the name of the 3115 is 'Obaid Humayun' -> isn't it?
3) Normal Call Release
Call End Inbound H225 RELEASE_COMP message from 10.95.3.210 at timestamp 05/17/2011 16:47:55.991
RELEASE_COMP, pd = 8, callref = 0x8004, Message Size = 46 bytes
Cause i = 0x8190 - Normal call clearing
After that i think Obaid Humayun dialed back to you
1) Call Setup
Inbound H225 SETUP message from 10.95.3.210 at timestamp 05/17/2011 16:47:58.444
SETUP, pd = 8, callref = 0x097A, Message Size = 219 bytes
Bearer Capability i = 0x9090A3, ITU-T standard, 3.1kHz audio, Circuit mode, 64k, A-law
Display i = 'Obaid Humayun'
Called Party Number i = Plan: Unknown, Type: Unknown
User-User, i =
2) The CuCM isn't seeing any Called Party Number
3) Release Message from CuCM can't route the Call
Outbound H225 RELEASE_COMP message to 10.95.3.210 at timestamp 05/17/2011 16:47:58.460
RELEASE_COMP, pd = 8, callref = 0x897A, Message Size = 45 bytes
Cause i = 0x80A9 - Temporary failure
User-User, i = 0x052580060008914A000201110000FE20657F88E001D4074C2792EA00000A800100
So this is the Debug Message you see on your Avaya Switch.
Maybe look at your Avaya why this isn't sending Dialed Digits to the CuCM
To Read the CuCM Traces more comfortable i read it with TranslatorX (from a Cisco Guy called Paul Giralt)
http://www.employees.org/~pgiralt/TranslatorX/<http://www.employees.org/%7Epgiralt/TranslatorX/>
cheers Floh
Am 18.05.2011 18:06, schrieb Humayun Sami/Engineering/Karachi:
Thx Florian.
John can you please mention that were you facing the same problem, which the calls were only going from Cisco to Avaya and not from Avaya to Cisco.
Regards,
Humayun Sami.
________________________________
From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bantz John F
Sent: Wednesday, May 18, 2011 8:39 PM
To: Florian Kroessbacher; Humayun Sami
Cc: <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [spam] Re: [cisco-voip] Avaya and CCM 4.3 Integration over H323 Trunk
Thanks for the tip Florian!
We do have a calling search space defined under the Call Routing Information - Inbound Calls section, but no AAR Calling Search Space.
We did get the trunk up and working last week. The problem was that we did not have a special application in our Avaya system turned on. There is a special application called "SA 8507 - H245 support with other vendors" that needed to be turned on in the Avaya system before we could get the connection up and running. After getting that turned on, the only other thing we had to do was to turn off Enable Outbound FastStart on the Cisco gateway and it worked great!
Thanks
John Bantz
John Deere - Global Infrastructure Services
515-267-4628 - office
515-314-6478 - cell
BantzJohnF at JohnDeere.Com<mailto:BantzJohnF%40JohnDeere.Com>
CONFIDENTIALITY. This electronic mail and any files transmitted with it may contain information proprietary to Deere & Company, or one of its subsidiaries or affiliates, and are intended solely for the use of the individual or entity to whom they are addressed, shall be maintained in confidence and not disclosed to third parties without the written consent of the sender. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.
From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Florian Kroessbacher
Sent: Wednesday, May 18, 2011 10:26 AM
To: Humayun Sami
Cc: <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Avaya and CCM 4.3 Integration over H323 Trunk
hy in the pdf they configure the gateway with no inbound calling search!
Maybe this is your problem. The GW has to have a inbound css to reaxh your cisco phones
----
Florian Kroessbacher
gmail: florian.kroessbacher at gmail.com<mailto:florian.kroessbacher at gmail.com>
Am 18.05.2011 um 17:11 schrieb Humayun Sami <humayun_sami at hotmail.com<mailto:humayun_sami at hotmail.com>>:
Hey Guys,
I have integrated Avaya and Cisco Call manager 4.3, I am able to make calls from Cisco to Avaya phones but Avaya phones cannot make call to Cisco. I have tried everything, made regions, device pool. Below is the link I followed for integration.
http://www.avaya.com/master-usa/en-us/resource/assets/applicationnotes/ip-trunk-cm.pdf
I am not getting the point that if the trunk has been established, why arnt the Avaya phones able to call cisco phones. Help in this regard would be nice. I am attaching the traces from CCM and below are the traces from Avaya with Denial Event 1192. Below it says seize trunk group, what does it mean?
Related Information to read logs:
Avaya gateway: 10.95.3.210
Call manager IP: 10.128.0.11
Avaya Phone: 3115
Cisco Phone:5528
Logs from Avaya:
VOIP data from: [10.95.3.213]:45424
12:30:48 Jitter:2 0 0 0 0 0 0 0 0 0: Buff:15 WC:8 Avg:1
12:30:48 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [10.95.3.213]:45424
12:30:56 Jitter:2 0 2 0 0 1 4 0 2 0: Buff:16 WC:8 Avg:1
12:30:56 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [10.95.3.213]:45424
12:31:06 Jitter:5 5 5 2 0 0 1 5 5 5: Buff:16 WC:8 Avg:2
12:31:06 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [10.95.3.213]:45424
12:31:16 Jitter:4 2 3 5 4 4 1 3 4 0: Buff:15 WC:8 Avg:2
12:31:16 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
12:31:19 hold station 3115 cid 0x1090
12:31:19 active announcement 7503 cid 0x1090
12:31:19 hear annc board 01B13 ext 7503 cid 0x1090
LIST TRACE
time data
12:31:20 active station 3115 cid 0x10a7
12:31:21 dial 811
12:31:21 term trunk-group 11 cid 0x10a7
12:31:21 dial 811
12:31:21 seize trunk-group 11 member 2 cid 0x10a7
12:31:21 Calling Number & Name NO-CPNumber Obaid Humayun
12:31:21 Proceed trunk-group 11 member 2 cid 0x10a7
12:31:21 denial event 1192: Temporary failure D1=0x8bbb D2=0x50f29
12:31:21 idle trunk-group 11 member 2 cid 0x10a7
12:31:24 idle station 3115 cid 0x10a7
12:31:24 unhold station 3115 cid 0x1090
12:32:14 TRACE COMPLETE station 3115 cid 0x1
Regards,
Humayun Sami.
<ccmavay00000000.txt>
<ccmavay00000001.txt>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110519/f8192c67/attachment.html>
More information about the cisco-voip
mailing list