Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: VOIP

Avaya - CCM v5 Integration

 

 

Cisco voip RSS feed   Index | Next | Previous | View Threaded


James.Jung at telecom

Feb 18, 2009, 6:32 PM

Post #1 of 10 (1741 views)
Permalink
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.


jason.aarons at us

Feb 18, 2009, 7:20 PM

Post #2 of 10 (1686 views)
Permalink
Re: Avaya - CCM v5 Integration [In reply to]

I believe you need to use QSIG over MGCP.



From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of James Jung
Sent: Wednesday, February 18, 2009 9:32 PM
To: cisco-voip [at] puck
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.


JASON.BURWELL at foundersfcu

Feb 19, 2009, 5:57 AM

Post #3 of 10 (1680 views)
Permalink
Re: Avaya - CCM v5 Integration [In reply to]

James,

It may have something to go with the version of G3si you are
running. R7 is ancient and was Avaya's first attempt at IP capability.
As I recall, R7 was barely out when they dumped it for R8.2 since R7 had
so many bugs. It was not until R8.4 that IP functions and the release in
general was stable. Just a possibility.

Jason

Jason Burwell
Telecom Network Administrator
Founders Federal Credit Union


Notice: All statements and representations in this transmission are not
necessarily those of my employer.


________________________________

From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of James Jung
Sent: Wednesday, February 18, 2009 9:32 PM
To: cisco-voip [at] puck
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.


James.Jung at telecom

Feb 19, 2009, 2:40 PM

Post #4 of 10 (1685 views)
Permalink
Re: Avaya - CCM v5 Integration [In reply to]

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]
Sent: Thursday, 19 February 2009 16:21
To: James Jung; cisco-voip [at] puck
Subject: RE: [cisco-voip] Avaya - CCM v5 Integration



I believe you need to use QSIG over MGCP.



From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of James Jung
Sent: Wednesday, February 18, 2009 9:32 PM
To: cisco-voip [at] puck
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.


wsisk at cisco

Feb 19, 2009, 3:24 PM

Post #5 of 10 (1673 views)
Permalink
Re: Avaya - CCM v5 Integration [In reply to]

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> 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]
> Sent: Thursday, 19 February 2009 16:21
> To: James Jung; cisco-voip [at] puck
> Subject: RE: [cisco-voip] Avaya - CCM v5 Integration
>
>
>
> I believe you need to use QSIG over MGCP.
>
>
>
> From: cisco-voip-bounces [at] puck
> [mailto:cisco-voip-bounces [at] puck] On Behalf Of James Jung
> Sent: Wednesday, February 18, 2009 9:32 PM
> To: cisco-voip [at] puck
> 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
> https://puck.nether.net/mailman/listinfo/cisco-voip
>


James.Jung at telecom

Feb 19, 2009, 4:55 PM

Post #6 of 10 (1695 views)
Permalink
Re: Avaya - CCM v5 Integration [In reply to]

Hi Wes



Thanks for commenting.

I tried that but it didn't work. CUCM HELP shows following. Looks like
it's about outgoing call.

Enable Display IE in Codeset 6: This parameter determines whether Cisco
CallManager sends the Q931 display information element (IE) in codeset 6
for the PRI 4ESS protocol type SETUP and CONNECT messages. Valid values
specify True (Cisco CallManager sends Q931 display IE in codeset 6) or
False (Cisco CallManager sends Q931 display IE in codeset 0). Keep this
parameter set to the default value unless a Cisco support engineer
instructs otherwise. This is a required field. Default: False



My problem is incoming call from Avaya phone. Calling name is not
displayed on Cisco IP Phone.



Any other way??



Thanks and Regards

James Jung
Senior Systems Support Specialist, IPST

________________________________

From: Wes Sisk [mailto:wsisk [at] cisco]
Sent: Friday, 20 February 2009 12:24
To: James Jung
Cc: cisco-voip [at] puck
Subject: Re: [cisco-voip] Avaya - CCM v5 Integration



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> <mailto:James.Jung [at] telecom> 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]
Sent: Thursday, 19 February 2009 16:21
To: James Jung; cisco-voip [at] puck
Subject: RE: [cisco-voip] Avaya - CCM v5 Integration



I believe you need to use QSIG over MGCP.



From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of James Jung
Sent: Wednesday, February 18, 2009 9:32 PM
To: cisco-voip [at] puck
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
https://puck.nether.net/mailman/listinfo/cisco-voip


wsisk at cisco

Feb 19, 2009, 5:32 PM

Post #7 of 10 (1742 views)
Permalink
Re: Avaya - CCM v5 Integration [In reply to]

Hi James,

Several enhancements requesting that but all are closed. Only 1 request
was resolved which was that one. Frequently enabling egress enables
ingress. Unfortunately does not appear possible.

/wes

On Thursday, February 19, 2009 7:55:56 PM, James Jung
<James.Jung [at] telecom> wrote:
> Hi Wes
>
>
>
> Thanks for commenting.
>
> I tried that but it didn't work. CUCM HELP shows following. Looks like
> it's about outgoing call.
>
> Enable Display IE in Codeset 6: This parameter determines whether Cisco
> CallManager sends the Q931 display information element (IE) in codeset 6
> for the PRI 4ESS protocol type SETUP and CONNECT messages. Valid values
> specify True (Cisco CallManager sends Q931 display IE in codeset 6) or
> False (Cisco CallManager sends Q931 display IE in codeset 0). Keep this
> parameter set to the default value unless a Cisco support engineer
> instructs otherwise. This is a required field. Default: False
>
>
>
> My problem is incoming call from Avaya phone. Calling name is not
> displayed on Cisco IP Phone.
>
>
>
> Any other way??
>
>
>
> Thanks and Regards
>
> James Jung
> Senior Systems Support Specialist, IPST
>
> ________________________________
>
> From: Wes Sisk [mailto:wsisk [at] cisco]
> Sent: Friday, 20 February 2009 12:24
> To: James Jung
> Cc: cisco-voip [at] puck
> Subject: Re: [cisco-voip] Avaya - CCM v5 Integration
>
>
>
> 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> <mailto:James.Jung [at] telecom> 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]
> Sent: Thursday, 19 February 2009 16:21
> To: James Jung; cisco-voip [at] puck
> Subject: RE: [cisco-voip] Avaya - CCM v5 Integration
>
>
>
> I believe you need to use QSIG over MGCP.
>
>
>
> From: cisco-voip-bounces [at] puck
> [mailto:cisco-voip-bounces [at] puck] On Behalf Of James Jung
> Sent: Wednesday, February 18, 2009 9:32 PM
> To: cisco-voip [at] puck
> 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
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
>

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip


dwinkworth at att

Feb 20, 2009, 4:38 AM

Post #8 of 10 (1715 views)
Permalink
Re: Avaya - CCM v5 Integration [In reply to]

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> 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]
>> Sent: Thursday, 19 February 2009 16:21
>> To: James Jung; cisco-voip [at] puck
>> Subject: RE: [cisco-voip] Avaya - CCM v5 Integration
>>
>>
>>
>> I believe you need to use QSIG over MGCP.
>>
>>
>>
>> From: cisco-voip-bounces [at] puck
>> [mailto:cisco-voip-bounces [at] puck] On Behalf Of James Jung
>> Sent: Wednesday, February 18, 2009 9:32 PM
>> To: cisco-voip [at] puck
>> 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
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> 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
https://puck.nether.net/mailman/listinfo/cisco-voip


dwinkworth at att

Feb 20, 2009, 4:41 AM

Post #9 of 10 (1669 views)
Permalink
Re: Avaya - CCM v5 Integration [In reply to]

Ahh..

I meant ISO QSIG.. sorry...

Derick Winkworth wrote:
> 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> 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]
>>> Sent: Thursday, 19 February 2009 16:21
>>> To: James Jung; cisco-voip [at] puck
>>> Subject: RE: [cisco-voip] Avaya - CCM v5 Integration
>>>
>>>
>>>
>>> I believe you need to use QSIG over MGCP.
>>>
>>>
>>>
>>> From: cisco-voip-bounces [at] puck
>>> [mailto:cisco-voip-bounces [at] puck] On Behalf Of James Jung
>>> Sent: Wednesday, February 18, 2009 9:32 PM
>>> To: cisco-voip [at] puck
>>> 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
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip [at] puck
>> 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
> 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
https://puck.nether.net/mailman/listinfo/cisco-voip


jason.aarons at us

Feb 20, 2009, 10:56 AM

Post #10 of 10 (1695 views)
Permalink
Re: Avaya - CCM v5 Integration [In reply to]

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

-----Original Message-----
From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] 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> 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]
>> Sent: Thursday, 19 February 2009 16:21
>> To: James Jung; cisco-voip [at] puck
>> Subject: RE: [cisco-voip] Avaya - CCM v5 Integration
>>
>>
>>
>> I believe you need to use QSIG over MGCP.
>>
>>
>>
>> From: cisco-voip-bounces [at] puck
>> [mailto:cisco-voip-bounces [at] puck] On Behalf Of James Jung
>> Sent: Wednesday, February 18, 2009 9:32 PM
>> To: cisco-voip [at] puck
>> 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
>>
>> Feb 10 14:42:19: ISDN Se0/0/1:15 Q931: RX <- DISCONNECT pd = 8
callref
>>
>>
>>
>>
>>
>>
>>
>> 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
>>
>> 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
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> 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
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.
_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
https://puck.nether.net/mailman/listinfo/cisco-voip

Cisco voip RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.