[cisco-voip] Avaya - CCM v5 Integration

Jason Aarons (US) jason.aarons at us.didata.com
Fri Feb 20 13:56:09 EST 2009


He may not have QSIG feature license on the Avaya.....

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Derick
Winkworth
Sent: Friday, February 20, 2009 7:38 AM
To: Cisco VoIP
Subject: Re: [cisco-voip] Avaya - CCM v5 Integration

Hmm..

Just to try it... why don't you enable IOS QSIG on the PRI between the
gateway and the Avaya. 

Also, I believe you can configure the Avaya to populate the unknown
number with something.



Wes Sisk wrote:
> try changing cm service parameter "Enable Display IE in Codeset 6".
>
> /Wes
>
>
>
> On Thursday, February 19, 2009 5:40:06 PM, James Jung
> <James.Jung at telecom.co.nz> wrote:
>> Thanks for the comments guys.
>>
>>  
>>
>> Anyone knows about   "   Codeset 6 IE 0x28  i = 'Russel McAuliff'
"
>> ?
>>
>> What does it do?
>>
>> Does MGCP support this?  Because with H323 it worked but with mgcp,
it
>> works only if there's calling number present.
>>
>> I saw two types.
>>
>> 1. Both calling number and name is seen on Q931. Then, Cisco IP phone
>> displays only calling name.
>>
>> 2. No calling number is seen and only calling name is seen on Q931.
>> Then, Cisco IP phone displays nothing.
>>
>> I don't know why calling name is not displayed.
>>
>>  
>>
>> ________________________________
>>
>> From: Jason Aarons (US) [mailto:jason.aarons at us.didata.com] 
>> Sent: Thursday, 19 February 2009 16:21
>> To: James Jung; cisco-voip at puck.nether.net
>> Subject: RE: [cisco-voip] Avaya - CCM v5 Integration
>>
>>  
>>
>> I believe you need to use QSIG over MGCP.
>>
>>  
>>
>> From: cisco-voip-bounces at puck.nether.net
>> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of James Jung
>> Sent: Wednesday, February 18, 2009 9:32 PM
>> To: cisco-voip at puck.nether.net
>> Subject: [cisco-voip] Avaya - CCM v5 Integration
>>
>>  
>>
>> Hi, Gurus
>>
>>  
>>
>> I have a customer who use Avaya G3si V7 and CCM v5.1.3.
>>
>> Voice GW is connected to Avaya PBX through PRI-5net. CCM is using
MGCP. 
>>
>> (( CCM - Voice GW - Avaya - PSTN ))
>>
>>  
>>
>> The problem is when Avaya phone calls to Cisco IP phones, the calling
>> name is not displayed on the IP phones.
>>
>>  
>>
>> Before this, we used H.323 and at that time, the calling name was
>> displayed on the Cisco IP phones, but after changing to MGCP, nothing
is
>> displayed.
>>
>>  
>>
>> I'd really appreciate if anyone can help me on this.
>>
>>  
>>
>>  
>>
>> Below is the Q931 debug messages that shows calls from avaya phone to
>> cisco IP phone.
>>
>>  
>>
>>  
>>
>> Feb 10 14:42:04: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8  callref =
>> 0x2E05 
>>
>>         Sending Complete 
>>
>>         Bearer Capability i = 0x9090A3 
>>
>>                 Standard = CCITT 
>>
>>                 Transfer Capability = 3.1kHz Audio 
>>
>>                 Transfer Mode = Circuit 
>>
>>                 Transfer Rate = 64 kbit/s 
>>
>>         Channel ID i = 0xA18385 
>>
>>                 Preferred, Channel 5 
>>
>>         Progress Ind i = 0x8183 - Origination address is non-ISDN  
>>
>>         Called Party Number i = 0x80, '3940' 
>>
>>                 Plan:Unknown, Type:Unknown 
>>
>>         Locking Shift to Codeset 6 
>>
>>         Codeset 6 IE 0x28  i = 'Russel McAuliff'
>>
>> Feb 10 14:42:04: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8
callref =
>> 0xAE05 
>>
>>         Channel ID i = 0xA98385 
>>
>>                 Exclusive, Channel 5
>>
>> Feb 10 14:42:04: ISDN Se0/0/1:15 Q931: TX -> ALERTING pd = 8  callref
=
>> 0xAE05 
>>
>>         Progress Ind i = 0x8088 - In-band info or appropriate now
>> available 
>>
>> Feb 10 14:42:07: ISDN Se0/0/1:15 Q931: TX -> CONNECT pd = 8  callref
=
>> 0xAE05 
>>
>>         Display i = 'Lois Mckay'
>>
>> Feb 10 14:42:07: ISDN Se0/0/1:15 Q931: RX <- CONNECT_ACK pd = 8
callref
>> = 0x2E05
>>
>> Feb 10 14:42:19: ISDN Se0/0/1:15 Q931: RX <- DISCONNECT pd = 8
callref
>> = 0x2E05 
>>
>>  
>>
>>  
>>
>>  
>>
>> Feb 10 14:44:37: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8  callref =
>> 0x2E92 
>>
>>         Sending Complete 
>>
>>         Bearer Capability i = 0x9090A3 
>>
>>                 Standard = CCITT 
>>
>>                 Transfer Capability = 3.1kHz Audio 
>>
>>                 Transfer Mode = Circuit 
>>
>>                 Transfer Rate = 64 kbit/s 
>>
>>         Channel ID i = 0xA18388 
>>
>>                 Preferred, Channel 8 
>>
>>         Progress Ind i = 0x8183 - Origination address is non-ISDN  
>>
>>         Calling Party Number i = 0xA1, '3095' 
>>
>>                 Plan:ISDN, Type:National 
>>
>>         Called Party Number i = 0x80, '3940' 
>>
>>                 Plan:Unknown, Type:Unknown 
>>
>>         Locking Shift to Codeset 6 
>>
>>         Codeset 6 IE 0x28  i = 'David Franklin'
>>
>> Feb 10 14:44:37: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8
callref =
>> 0xAE92 
>>
>>         Channel ID i = 0xA98388 
>>
>>                 Exclusive, Channel 8
>>
>> Feb 10 14:44:37: ISDN Se0/0/1:15 Q931: TX -> ALERTING pd = 8  callref
=
>> 0xAE92 
>>
>>         Progress Ind i = 0x8088 - In-band info or appropriate now
>> available 
>>
>> Feb 10 14:44:38: ISDN Se0/0/1:15 Q931: RX <- CONNECT pd = 8  callref
=
>> 0x81C1 
>>
>>         Progress Ind i = 0x8282 - Destination address is non-ISDN  
>>
>>         Date/Time i = 0x09020A0E2C 
>>
>>                 Date (yr-mm-dd)   = 09-02-10 
>>
>>                 Time (hr:mnt:sec) = 14:44:164
>>
>> Feb 10 14:44:38: ISDN Se0/0/1:15 Q931: TX -> CONNECT_ACK pd = 8
callref
>> = 0x01C1
>>
>> Feb 10 14:44:57: ISDN Se0/0/1:15 Q931: TX -> CONNECT pd = 8  callref
=
>> 0xAE92
>>
>> Feb 10 14:44:57: ISDN Se0/0/1:15 Q931: RX <- CONNECT_ACK pd = 8
callref
>> = 0x2E92
>>
>>  
>>
>> Thanks and regards,
>>
>> James.
>>
>>  
>>
>> ________________________________
>>
>> Disclaimer: This e-mail communication and any attachments may contain
>> confidential and privileged information and is for use by the
designated
>> addressee(s) named above only. If you are not the intended addressee,
>> you are hereby notified that you have received this communication in
>> error and that any use or reproduction of this email or its contents
is
>> strictly prohibited and may be unlawful. If you have received this
>> communication in error, please notify us immediately by replying to
this
>> message and deleting it from your computer. Thank you. 
>>
>>
>>   
>>
------------------------------------------------------------------------
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>   
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   
>
------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com 
> Version: 8.0.237 / Virus Database: 270.11.1/1961 - Release Date:
02/19/09 18:45:00
>
>   
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.


More information about the cisco-voip mailing list