Avaya IP trunks hairpin calls

[srmega41]

OK, I have a IP Enabled (using C-Lan and medpro boards) G3R PBX at my core. Version 12i.01.1.414 connected to a new S8300 G350 using IP trunks. The G350 is version 3x.01.4.642. The problem is calls are not being torn down as they go back and forth. I called this tromboning in my Nortel days, and Avaya seems to use the term Hairpinning. Anyways, here is what happens when a caller calls from the G3R to the G350:

TRUNK GROUP STATUS

Member Port Service State Mtce Connected Ports
Busy

0010/001 T00001 in-service/active no T00008
0010/002 T00002 in-service/idle no
0010/003 T00003 in-service/idle no
0010/004 T00004 in-service/idle no
0010/005 T00005 in-service/idle no
0010/006 T00006 in-service/idle no
0010/007 T00007 in-service/idle no
0010/008 T00008 in-service/active no T00001
0010/009 T00009 in-service/idle no
0010/010 T00010 in-service/idle no

As you can see, trunk 1 and 8 are tied together. If I stat the trunks on the other side, I get the same thing:

Member Port Service State Mtce Connected Ports
Busy

10/01 T00081 in-service/active no S00038
10/02 T00082 in-service/active no T00084
10/03 T00083 in-service/idle no
10/04 T00084 in-service/active no T00082
10/05 T00085 in-service/idle no
10/06 T00086 in-service/idle no
10/07 T00087 in-service/idle no
10/08 T00088 in-service/active no 01D0201
10/09 T00089 in-service/idle no
10/10 T00090 in-service/idle no

You can also see a few other calls in progress, but trunks 2 and 4 are tied together for this call. My displays both also show the IP Phone at the G350 side on their display, not each other as they should.

Any ideas? I would assume there needs to be a change either on the trunk or signaling group, but I am not as well versed on the Avaya side as I am Nortel, so I am hoping for a little help here. This also creates a big voicemail issue, because of multiple encodings. Let me know if you need other info, and I will be happy to post them.

Thanks for looking,

Scott

 

[nohuhu]

srmega41,

you're confusing terms. hairpinning is a feature that allows passing voip packets through the voip interface (medpro, crossfire, etc) but without entering tdm bus. useful in nat/firewall environments where it's easier to control rtp traffic emitting from one ip address rather than from hundreds or thousands. so it's not a bug.
please show your ip trunk settings, it may help.

 

[srmega41]

OK, I guess the issues I had with Nortel and were documented in 2002 might have started me down the wrong "term" path. I had the same issue compared to the hairpinning term in an article I was interviewed for, so I have always assumed that was Avaya speak for Tromboning.

Ok, as for IP trunk settings, here you go:

                                TRUNK GROUP

Group Number: 10                   Group Type: isdn          CDR Reports: y
  Group Name: DCS to Legacy               COR: 50       TN: 1        TAC: 706
   Direction: two-way        Outgoing Display? n         Carrier Medium: IP
 Dial Access? n                Busy Threshold: 99        Night Service:
Queue Length: 0
Service Type: tie                   Auth Code? n            TestCall ITC: unre
                         Far End Test Line No:
TestCall BCC: 0
TRUNK PARAMETERS
         Codeset to Send Display: 0     Codeset to Send National IEs: 6
        Max Message Size to Send: 260   Charge Advice: none
  Supplementary Service Protocol: a     Digit Handling (in/out): enbloc/enbloc

            Trunk Hunt: cyclical
                                                   Digital Loss Group: 18
Incoming Calling Number - Delete:     Insert:                 Format: pub-unk
              Bit Rate: 1200         Synchronization: async    Duplex: full
 Disconnect Supervision - In? y  Out? n
 Answer Supervision Timeout: 0



TRUNK FEATURES
          ACA Assignment? n            Measured: none      Wideband Support? n
                                 Internal Alert? n        Maintenance Tests? y
                               Data Restriction? n     NCA-TSC Trunk Member:
                                      Send Name: y      Send Calling Number: y
            Used for DCS? y  PBX ID: 10
   Suppress # Outpulsing? n    Format: public              DCS Signaling: d-chan
 Outgoing Channel ID Encoding: exclusive     UUI IE Treatment: service-provider

                                                 Replace Restricted Numbers? n
                                                Replace Unavailable Numbers? n
                                                      Send Connected Number: y
                                               Modify Tandem Calling Number? n
             Send UUI IE? y
               Send UCID? y
 Send Codeset 6/7 LAI IE? y



                     SBS? n  Network (Japan) Needs Connect Before Disconnect? n

Please let me know if you need anything else. Bottom line is there is no way a call into the G3R from the G350, then back again should use two trunks, right? Considering the voicemail is at the G3R, a call to the G350 would have to allow for trunk calls in and out, but should prune the redundant call path.

Thanks.

Scott M.

 

[srmega41]

Here are the trunk configs on the G350. Just took a power hit and that system was down as I was pulling them:

                                TRUNK GROUP

Group Number: 10                   Group Type: isdn          CDR Reports: y
  Group Name: DCS to City Hall            COR: 50       TN: 1        TAC: 706
   Direction: two-way        Outgoing Display? n         Carrier Medium: H.323
 Dial Access? n                Busy Threshold: 255       Night Service:
Queue Length: 0
Service Type: tie                   Auth Code? n
                                              Member Assignment Method: manual


      Group Type: isdn

TRUNK PARAMETERS
         Codeset to Send Display: 0     Codeset to Send National IEs: 6
                                        Charge Advice: none
  Supplementary Service Protocol: a     Digit Handling (in/out): enbloc/enbloc


                                                   Digital Loss Group: 18
Incoming Calling Number - Delete:     Insert:                 Format: pub-unk

 Disconnect Supervision - In? y  Out? n
 Answer Supervision Timeout: 0


TRUNK FEATURES
          ACA Assignment? n            Measured: none
                                 Internal Alert? n        Maintenance Tests? y
                               Data Restriction? n     NCA-TSC Trunk Member:
                                      Send Name: y      Send Calling Number: y
            Used for DCS? y  PBX ID: 1                 Send EMU Visitor CPN? n
   Suppress # Outpulsing? n    Format: public              DCS Signaling: d-chan
                                             UUI IE Treatment: service-provider

                                                 Replace Restricted Numbers? n
                                                Replace Unavailable Numbers? n
                                                      Send Connected Number: y
Network Call Redirection: none                    Hold/Unhold Notifications? n
             Send UUI IE? y                    Modify Tandem Calling Number? n
               Send UCID? y
 Send Codeset 6/7 LAI IE? y

 

[nohuhu]

srmega41,

i see one possible trouble point here: turn disconnect supervision in both directions on both trunks. also i'd like to see signaling groups on both sides.

 

[srmega41]

G3R side:

                                SIGNALING GROUP

 Group Number: 10             Group Type: h.323
                           Remote Office? n          Max number of NCA TSC: 1
                                     SBS? n           Max number of CA TSC: 1
                                                   Trunk Group for NCA TSC:
       Trunk Group for Channel Selection: 10
          Supplementary Service Protocol: a
                         T303 Timer(sec): 10

        Near-end Node Name: clan_CH01        Far-end Node Name: legacy_procr
      Near-end Listen Port: 1720           Far-end Listen Port: 1720
                                        Far-end Network Region:
              LRQ Required? n            Calls Share IP Signaling Connection? y
              RRQ Required? n
                                             Bypass If IP Threshold Exceeded? n

              DTMF over IP: out-of-band       Direct IP-IP Audio Connections? y
                                                        IP Audio Hairpinning? n
                                              Interworking Message: PROGress

                        ADMINISTERED NCA TSC ASSIGNMENT

Service/Feature:                      As-needed Inactivity Time-out (min):
 TSC   Local                                                             Mach.
Index   Ext.   Enabled Established    Dest. Digits    Appl.               ID
  1:  8099        y     permanent   8098             dcs                  10

G350 side

                                SIGNALING GROUP

 Group Number: 10             Group Type: h.323
                           Remote Office? n          Max number of NCA TSC: 1
                                     SBS? n           Max number of CA TSC: 1
                                IP Video? n        Trunk Group for NCA TSC:
       Trunk Group for Channel Selection: 10
          Supplementary Service Protocol: a          Network Call Transfer? n
                         T303 Timer(sec): 10

   Near-end Node Name: procr                 Far-end Node Name: city_hall_clan
 Near-end Listen Port: 1720                Far-end Listen Port: 1720
                                        Far-end Network Region: 1
         LRQ Required? n                 Calls Share IP Signaling Connection? y
         RRQ Required? n
     Media Encryption? n                     Bypass If IP Threshold Exceeded? n
                                                      H.235 Annex H Required? n
         DTMF over IP: out-of-band            Direct IP-IP Audio Connections? y
                                                        IP Audio Hairpinning? n
                                                 Interworking Message: PROGress
                                         DCP/Analog Bearer Capability: 3.1kHz

                        ADMINISTERED NCA TSC ASSIGNMENT

Service/Feature:                      As-needed Inactivity Time-out (min):
 TSC   Local                                                    Adj.     Mach.
Index   Ext.   Enabled Established    Dest. Digits    Appl.     Name      ID
  1:  8098        y     permanent   8099             dcs                  1

Let me know if you need anything else. I will work on the answer supervision change.

Thanks

 

[srmega41]

Answer supervision has no impact.

Thanks, have our vendor on site, and they seem to be a little stumped as well. BTW, I read the blurb on IP Audio Hairpinning, and I understand why you made mention of it on your post.

Our issue is more related to the actual trunk, but I appreciate the info and education.

Thanks, any other ideas???