H323 Trunking Alcatel OXE to Avaya IP Office

A H323 and SIP forum only !
rajansuruli15
Member
Posts: 58
Joined: 16 May 2013 02:23

H323 Trunking Alcatel OXE to Avaya IP Office

Post by rajansuruli15 » 11 Mar 2016 07:19

Hi everyone,

i am configuring H323 trunking between Alcatel OXE(common HW) to Avaya IP office.

1.Created TG with ISDN All countries, T2 specification as "IP"
2.Mapped to the GD3 card in TG third lvl.
3.created a prefix as professional TG siezer.
4.configured the avaya PBX number in direact speed dialing. Inside the call number is prefix+the avaya Pbx number and mentioned the avaya PBX IP also.

But i am getting below error. when i dial avaya PBX number.

(1)nic_pbx>
(1)nic_pbx> t3
--> Cleaning mtracer...
--> Positionning t3 filters...
+--------+-------+--------+--------+---------+---------+----------+------+
| filter | desti | src_id | cr_nbr | cpl_nbr | us_term | term_nbr | type |
+--------+-------+--------+--------+---------+---------+----------+------+
| 0 | ** | ** | * | ** | * | *** | 165 |
| 1 | ** | ** | * | ** | * | *** | 166 |
| 2 | ** | ** | * | ** | * | *** | 167 |
| 3 | | | | | | | |
| 4 | | | | | | | |
| 5 | | | | | | | |
| 6 | | | | | | | |
| 7 | | | | | | | |
+--------+-------+--------+--------+---------+---------+----------+------+
Traces Analyser activated
mtracer started ...
(090849:000001) MTRACER host (192.168.15.1, nic_pbx), version: R9.1-i1.605-25-b-
ke-c82
(090849:000001) MTRACER num: 013, time: 2016/03/10 13:31:06, loss: 0%
______________________________________________________________________________
| (090872:000002) 1299: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 70 desti: 0 source: 15 cryst: 2 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 45
|______________________________________________________________________________
|
| [9f] Non-locking shift. codeset : 7
| [a2] EI_IP_TYPE_TERM
| [9f] Non-locking shift. codeset : 7
| IE:[05] EI_IP_INFOS (l=9) -> G723 Ece 1 Vad 0 Profil 2, IPv4 :10.13.16.30.
| [9f] Non-locking shift. codeset : 7
| IE:[06] EI_IP_PAYLOADS (l=1) -> G729 Ece 1 Vad 0
| [9f] Non-locking shift. codeset : 7
| IE:[07] EI_IP_QOS (l=3) b8 a0 00
| [9f] Non-locking shift. codeset : 7
| IE:[0a] EI_RTP_INFO (l=2)
| -> stop_packet=0 stop_rtp=0 h323=0 wc=0 rf=0 udp=1 rqm=0
| -> Transm_Bande=1 detection_Q23=1 dtmf_payload=96
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[6c] CALLING_NUMBER (l=5) -> 01 81 Num : 253
| IE:[70] CALLED_NUMBER (l=4) -> 81 Num : 138
| IE:[7d] HLC (l=2) 91 81
| [a1] Sending complete
|______________________________________________________________________________
______________________________________________________________________________
| (090873:000004) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 2 cpl: 0 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CALL PROC (02) Call ref : 80 45
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=2) a9 83 -> T2 : B channel
|______________________________________________________________________________
______________________________________________________________________________
| (090873:000005) 1299: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 26 desti: 0 source: 15 cryst: 2 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : STATUS [7d] Call ref : 00 45
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 81 e4 18 -> [e4] INVALID INFORMATION ELEMENT CONTENTS
| IE:[14] CALL_STATE (l=1) 01
|______________________________________________________________________________
______________________________________________________________________________
| (090873:000006) Concatenated-Physical-Event :
| long: 24 desti: 0 source: 0 cryst: 2 cpl: 0 us: 0 term: 0 type a5
| tei: 0 >>>> message received : DISCONNECT [45] Call ref : 80 45
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=4) 01 80 e5 7d -> [e5] MESSAGE NOT COMPATIBLE WITH CALL STATE
|______________________________________________________________________________
______________________________________________________________________________
| (090873:000007) 1299: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 2 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : RELEASE [4d] Call ref : 00 45
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________
______________________________________________________________________________
| (090874:000008) Concatenated-Physical-Event :
| long: 23 desti: 0 source: 0 cryst: 2 cpl: 0 us: 0 term: 0 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 80 45
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 01 80 80 -> [80] UNKNOWN
|______________________________________________________________________________
(1)nic_pbx>



I ignored the ISDN msg setting in mgr/system also. But still not working.

Anyone give some suggestion to help me to close the issue.

Regards,
Rajan K.S

sadim
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 500
Joined: 02 Jun 2006 07:11
Location: Portugal

Re: H323 Trunking Alcatel OXE to Avaya IP Office

Post by sadim » 11 Mar 2016 08:11

Hello,

On the IP trunk, is B Channel Choice set to True?

Regards

rajansuruli15
Member
Posts: 58
Joined: 16 May 2013 02:23

Re: H323 Trunking Alcatel OXE to Avaya IP Office

Post by rajansuruli15 » 12 Mar 2016 04:07

Hi sadim,

Thanks for the replay.

currently i configured "B" channel choice is "false". if i set B channel "True", getting Busy tone and in Trace showing "no B channel".

Regards,
Rajan K.S

sadim
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 500
Joined: 02 Jun 2006 07:11
Location: Portugal

Re: H323 Trunking Alcatel OXE to Avaya IP Office

Post by sadim » 12 Mar 2016 07:37

B channel choice must be set to true on a h323 cnx
Attach a trace with this configuration

Enviado do meu ALE-L21 através de Tapatalk

vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3465
Joined: 23 Sep 2004 06:47
Location: Russia

Re: H323 Trunking Alcatel OXE to Avaya IP Office

Post by vad » 12 Mar 2016 11:06

Strange message from Avaya B channel but without indication witch B channel.

_____________________________________________________________________________
| (090873:000004) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 2 cpl: 0 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CALL PROC (02) Call ref : 80 45
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=2) a9 83 -> T2 : B channel
|______________________________________________________________________________

sadim
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 500
Joined: 02 Jun 2006 07:11
Location: Portugal

Re: H323 Trunking Alcatel OXE to Avaya IP Office

Post by sadim » 12 Mar 2016 17:09

Hello Vad,

My best guess is that this is due the missing of the channel (IE:[18] CHANNEL (l=3) a8 83 81 -> T2 : No B channel) in the setup msg that was sent by OXE.
Also, RTP and RTPC ports are missing on Setup, but once again, i believe that is due the fact that he has B Channel Choice at False,
He must provide a new trace with B Channel Choice at True.

Best Regards

rajansuruli15
Member
Posts: 58
Joined: 16 May 2013 02:23

Re: H323 Trunking Alcatel OXE to Avaya IP Office

Post by rajansuruli15 » 15 Mar 2016 05:05

Hello saidm & vlad,

Please fidn the below traces, when i configure "B channel Choice is True".

(1)nic_pbx> t3
--> Cleaning mtracer...
--> Positionning t3 filters...
+--------+-------+--------+--------+---------+---------+----------+------+
| filter | desti | src_id | cr_nbr | cpl_nbr | us_term | term_nbr | type |
+--------+-------+--------+--------+---------+---------+----------+------+
| 0 | ** | ** | * | ** | * | *** | 165 |
| 1 | ** | ** | * | ** | * | *** | 166 |
| 2 | ** | ** | * | ** | * | *** | 167 |
| 3 | | | | | | | |
| 4 | | | | | | | |
| 5 | | | | | | | |
| 6 | | | | | | | |
| 7 | | | | | | | |
+--------+-------+--------+--------+---------+---------+----------+------+
Traces Analyser activated
mtracer started ...
(369489:000001) MTRACER host (192.168.15.1, nic_pbx), version: R9.1-i1.605-25-b-
ke-c82
(369489:000001) MTRACER num: 017, time: 2016/03/15 12:22:19, loss: 0%
______________________________________________________________________________
| (369516:000002) 1298: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 103 desti: 0 source: 15 cryst: 2 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 61
|______________________________________________________________________________
|
| [9f] Non-locking shift. codeset : 7
| [a2] EI_IP_TYPE_TERM
| [9f] Non-locking shift. codeset : 7
| IE:[05] EI_IP_INFOS (l=9) -> G723 Ece 1 Vad 0 Profil 2, IPv4 :10.13.16.30.
| [9f] Non-locking shift. codeset : 7
| IE:[06] EI_IP_PAYLOADS (l=1) -> G729 Ece 1 Vad 0
| [9f] Non-locking shift. codeset : 7
| IE:[07] EI_IP_QOS (l=3) b8 a0 00
| [9f] Non-locking shift. codeset : 7
| IE:[0a] EI_RTP_INFO (l=30)
| -> stop_packet=0 stop_rtp=0 h323=0 wc=0 rf=0 udp=1 rqm=0
| -> Transm_Bande=1 detection_Q23=1 dtmf_payload=96
| -> Port RTP = 32514, IPv4 : 192. 168. 1. 221.
| -> Port RTCP SR = 32515, IPv4 : 192. 168. 1. 221.
| -> Port RTCP RR = 32515, IPv4 : 192. 168. 1. 221.
| -> Port Fax = 0, IPv4 : 0. 0. 0. 0.
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a8 83 81 -> T2 : No B channel
| IE:[6c] CALLING_NUMBER (l=5) -> 01 81 Num : 253
| IE:[70] CALLED_NUMBER (l=4) -> 81 Num : 138
| IE:[7d] HLC (l=2) 91 81
| [a1] Sending complete
|______________________________________________________________________________
______________________________________________________________________________
| (369517:000004) Concatenated-Physical-Event :
| long: 21 desti: 0 source: 0 cryst: 2 cpl: 0 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CALL PROC (02) Call ref : 80 61
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=1) a8 -> T2 : No B channel
|______________________________________________________________________________
______________________________________________________________________________
| (369576:000005) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 2 cpl: 0 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : 80 61
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 83 -> [83] NO ROUTE TO DESTINATION
|______________________________________________________________________________
______________________________________________________________________________
| (369576:000006) 1298: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 2 cpl: 0 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : 00 61
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________


I am getting busy tone, when i dial the Avaya PBX extension number.

Sorry ..had little delay on uploading this trace..

please share your suggestions ...

Thanks & Regards,
Rajan K.S

sadim
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 500
Joined: 02 Jun 2006 07:11
Location: Portugal

Re: H323 Trunking Alcatel OXE to Avaya IP Office

Post by sadim » 15 Mar 2016 08:37

Hello,

Time to check in Avaya system, the reason of No Route to Destination.
138 is a Avaya internal Set, G729/G723 are ok for Avaya ?

Regards

rajansuruli15
Member
Posts: 58
Joined: 16 May 2013 02:23

Re: H323 Trunking Alcatel OXE to Avaya IP Office

Post by rajansuruli15 » 21 Mar 2016 08:15

hi,

Sorry for the delay replay. Avaya guy is saying that he added all the codecs available in the system.

And in our trace, its showing that "no B channel" is that normal...?

Thanks

User avatar
cavagnaro
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 7001
Joined: 14 Sep 2005 19:45
Location: Brasil, Porto Alegre
Contact:

Re: H323 Trunking Alcatel OXE to Avaya IP Office

Post by cavagnaro » 21 Mar 2016 08:35

138 is a Avaya internal Set? As sadim asks, seems maybe to be a remote set over other network. Ask Avaya guys for their logs.
Ignorance is not the problem, the problem is the one who doesn't want to learn

OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer

Post Reply

Return to “H323 / Sip”