QSIG Trunk between Avaya and 2821 caller ID number issue

Answered Question
Dec 10th, 2009

Hey guys --


I have a QSIG trunk between my H323 gateway and an Avaya G3R/8700 hybrid...


Everything works fine except Caller ID.  When the Avaya phone dials the Cisco IP Phone we currently get the trunk outside number instead of the calling party number.  When the Cisco Phone dials Avaya, caller ID works no problem.


In the Avaya, the PBX engineer says that she can change the format on the trunk group to unknown (from private), and that will show unknown name/number on the Cisco Phone.  She thinks that the problem is somewhere in the system the number is being masked, but she doesn't know where..


Any ideas?


Thanks guys.  (BTW not a fan of the NetPro 2.0...)


Ohamien

Correct Answer by Greg Cording about 7 years 2 months ago

Hi

    Get the tech to check Page 2 of the trunk form and confirm:


   The Numbering Format is set to public.

    Send Calling Number is Yes

    Send Connected number set to yes if you want to the connected number to be displayed on the tandemed call.


trunk.JPG



   Then goto change isdn public-unknown-numbering set:


   numbering format.JPG


   Extension Length (number of digits on the extension number)

   Extension Code (the leading digit of the Extension range)

   Trk Grup of the tie circuit

   Leave CPN prefix Blank

   Total CPN Length (total digits in the numbering plan e.g. 5 for 1xxxxx)


    That should do it..


   Also get the tech to run a List Trac TAC XXX where XXX is the TAC: adminsitered on Page 1 (top right) of the tie trunk group.


   Let me know how you get on.


  Cheers Greg


  www.linkedin.com/in/gcording

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
Loading.
ouhakheme Thu, 12/10/2009 - 13:59

I have some debugs that may help some..


When calling party is set to 'unknown-private'


*Dec 10 2009 21:59:11.084 UTC: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8  callref = 0x124F

        Sending Complete

        Bearer Capability i = 0x9090A2

                Standard = CCITT

                Transfer Capability = 3.1kHz Audio

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA18381

                Preferred, Channel 1

        Facility i = 0x9FAA068001008201008B0100A11802020265020100800F44617669732C2043686572796C2041

        Progress Ind i = 0x8183 - Origination address is non-ISDN

        Called Party Number i = 0xC9, '84607'

                Plan:Private, Type:Subscriber(local)

        Locking Shift to Codeset 4

        Codeset 4 IE 0x31  i = 0x80

*Dec 10 2009 21:59:11.096 UTC: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0x924F

        Channel ID i = 0xA98381

                Exclusive, Channel 1


When calling party is set to 'unknown'



*Dec 10 2009 21:38:51.768 UTC: ISDN Se0/0/0:23 Q931: RX <- SETUP pd = 8  callref                                                                              = 0x7F83

        Sending Complete

        Bearer Capability i = 0x9090A2

                Standard = CCITT

                Transfer Capability = 3.1kHz Audio

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA18381

                Preferred, Channel 1

        Facility i = 0x9FAA068001008201008B0100A11802020261020100800F49532056495                                                                             349544F522035202020

        Progress Ind i = 0x8183 - Origination address is non-ISDN

        Calling Party Number i = 0x0080, 'XXXXXXXXXX' (trunk outside line)

                Plan:Unknown, Type:Unknown

        Called Party Number i = 0xC9, '84607'

                Plan:Private, Type:Subscriber(local)

        Locking Shift to Codeset 4

        Codeset 4 IE 0x31  i = 0x80

*Dec 10 2009 21:38:51.784 UTC: ISDN Se0/0/0:23 Q931: TX -> CALL_PROC pd = 8  cal                                                                             lref = 0xFF83

        Channel ID i = 0xA98381

                Exclusive, Channel 1

Correct Answer
Greg Cording Thu, 12/10/2009 - 14:53

Hi

    Get the tech to check Page 2 of the trunk form and confirm:


   The Numbering Format is set to public.

    Send Calling Number is Yes

    Send Connected number set to yes if you want to the connected number to be displayed on the tandemed call.


trunk.JPG



   Then goto change isdn public-unknown-numbering set:


   numbering format.JPG


   Extension Length (number of digits on the extension number)

   Extension Code (the leading digit of the Extension range)

   Trk Grup of the tie circuit

   Leave CPN prefix Blank

   Total CPN Length (total digits in the numbering plan e.g. 5 for 1xxxxx)


    That should do it..


   Also get the tech to run a List Trac TAC XXX where XXX is the TAC: adminsitered on Page 1 (top right) of the tie trunk group.


   Let me know how you get on.


  Cheers Greg


  www.linkedin.com/in/gcording

Greg Cording Thu, 12/10/2009 - 14:54

Hi

    Get the tech to check Page 2 of the trunk form and confirm:


   The Numbering Format is set to public.

    Send Calling Number is Yes

    Send Connected number set to yes if you want to the connected number to be displayed on the tandemed call.


trunk.JPG



   Then goto change isdn public-unknown-numbering set:


   numbering format.JPG


   Extension Length (number of digits on the extension number)

   Extension Code (the leading digit of the Extension range)

   Trk Grup of the tie circuit

   Leave CPN prefix Blank

   Total CPN Length (total digits in the numbering plan e.g. 5 for 1xxxxx)


    That should do it..


   Also get the tech to run a List Trac TAC XXX where XXX is the TAC: adminsitered on Page 1 (top right) of the tie trunk group.


   Let me know how you get on.


  Cheers Greg

ouhakheme Thu, 12/10/2009 - 15:03

Wow, thank you.  I know that the numbering format is currently set to unknown, or unknown private, so we will change it to public.


The Numbering format page is probably exactly what we are missing. (I guess this page changes depending on the numbering plan..  Could you re-upload that image, it doesn't look like it go through.


I'll let you know how it goes in the morning.


Thanks again,


Ohamien

Greg Cording Thu, 12/10/2009 - 15:33

About the 5th attempt to add the screen shot, keep getting unexpected error.. grrrr.


  Didnt really explain "list trace tac" this will show you what CPN Number and Name is being generated by the Avaya when setting up the call to CUCM.


  Assuming that the Avaya Communication Manager has a CLAn MedPro and RTUs you could setup a H.323 Trunk between the two systems, this would save you transport costs assuming both are on the same Corp Network.


  Cheers Greg

mightyking Thu, 12/10/2009 - 20:16

In page 2 of the "change trunk-group" change the value of the "Send Name" to "Y"

Also

In  "Change signaling-group" page change the value of  "Supplementary Service Protocol" to "a". CallManager only recognizes the "a" version of the Supplementary Service Protocol sent by Avaya.


MK

ouhakheme Fri, 12/11/2009 - 11:43

Hey guys --


I tried what Greg suggested and that worked like a champ!


Thanks for the assist!


Ohamien

Actions

This Discussion

Related Content