QSig between OXE 7.1 - Avaya Definity
Re: QSig between OXE 7.1 - Avaya Definity
From my point of view - not correct "Number of digits to send=0".
I prefer manage or "Number of digits to send=4", or (better) Number compatible with=1 (f.e.) and in Discriminator 1 rules - create 7, number of digits 4.
I prefer manage or "Number of digits to send=4", or (better) Number compatible with=1 (f.e.) and in Discriminator 1 rules - create 7, number of digits 4.
Re: QSig between OXE 7.1 - Avaya Definity
Configuration seems to be OK for 7670, but on the trace you test with 7671.
Can you show the trace with 7670 or to show the mngt og 7671
Can you show the trace with 7670 or to show the mngt og 7671
-
- Member
- Posts: 293
- Joined: 21 Jan 2017 02:57
Re: QSig between OXE 7.1 - Avaya Definity
Im getting same trace for 7670 also
-
- Member
- Posts: 293
- Joined: 21 Jan 2017 02:57
Re: QSig between OXE 7.1 - Avaya Definity
incompatible destination is showing i tried in two ways
Dailed prefix 20 +7670 same issue where 20 is Prof.Trk with overlap
dailled 7670 same issue
Dailed prefix 20 +7670 same issue where 20 is Prof.Trk with overlap
dailled 7670 same issue
-
- Member
- Posts: 293
- Joined: 21 Jan 2017 02:57
Re: QSig between OXE 7.1 - Avaya Definity
Is this issue from avaya side or oxe side ?
Re: QSig between OXE 7.1 - Avaya Definity
Incompatible destination - you have from Avaya site (check ch ds1 - parameter DSP/Analog Bearer Capability - 3,1 kHz?)
- cavagnaro
- Alcatel Unleashed Certified Guru
- Posts: 7014
- Joined: 14 Sep 2005 19:45
- Location: Brasil, Porto Alegre
- Contact:
Re: QSig between OXE 7.1 - Avaya Definity
Please Hussa, focus on one post only...you have duplicated the same question and having exactly same answers on both at the end
Enviado de meu E6633 usando Tapatalk
Enviado de meu E6633 usando Tapatalk
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
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
-
- Member
- Posts: 293
- Joined: 21 Jan 2017 02:57
Re: QSig between OXE 7.1 - Avaya Definity
OK Sorry Cavagnaro actually i connected CAT6A cable in Network port of PRAT2 in oxe is when i seizeing the trunk by dialing prefix 20 there is no led status in Busy led but Channels are showing "F" and incidents i can see that T2 dlap established
Whether the connection between oxe and avaya is correct or i need to connect to PBX port in PRA T2
Please advice me
Whether the connection between oxe and avaya is correct or i need to connect to PBX port in PRA T2
Please advice me
- cavagnaro
- Alcatel Unleashed Certified Guru
- Posts: 7014
- Joined: 14 Sep 2005 19:45
- Location: Brasil, Porto Alegre
- Contact:
Re: QSig between OXE 7.1 - Avaya Definity
If you see F and not hs means the boards are in sync, which is ok, what you expect
But as you have been advised already, you need to talk to Avaya guys and see why their pbx is not understanding what you just sent to it.
Enviado de meu E6633 usando Tapatalk
But as you have been advised already, you need to talk to Avaya guys and see why their pbx is not understanding what you just sent to it.
Enviado de meu E6633 usando Tapatalk
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
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
-
- Member
- Posts: 293
- Joined: 21 Jan 2017 02:57
Re: QSig between OXE 7.1 - Avaya Definity
Welcome to holidayinn_1
Alcatel-Lucent OmniPCX Enterprise
login: mtcl
Password:
Last login: Thu Aug 25 22:43:28 from 130.0.30.56
Alcatel-Lucent OmniPCX Enterprise
standard installation last performed: 02-Apr-2015 02:45:43
# The role of the CPU is MAIN
Application software identity
R11.1-l1.301-37-ae-c0
Business identification: R11.1
Release:
DELIVERY l1.301
Patch identification: 37
Dynamic patch identification: none
Country: ae
Cpu: c0
ACD VERSION
release : 11
bug_fixing : 2
protocol_id : 92
version_dy_hr_stat : 12
t3(1)holidayinn_1> 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 ...
(304551:000001) MTRACER host (130.0.30.10, holidayinn_1), version: R11.1-l1.301-37-ae-c0
(304551:000001) MTRACER num: 019, time: 2016/08/25 22:45:22, loss: 0%
______________________________________________________________________________
| (304596:000002) 1424: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 72 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 5e
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a1 83 85 -> T2 : B channel 5 preferred
| IE:[1c] FACILITY (l=26)
| [91] Discriminator of supplementary service applications
| [aa] NFE (l=6):
| [80] Source Entity (l=1) End_PTNX
| [82] Destination Entity (l=1) End_PTNX
| [8b] Interpretation APDU (l=1): DISCARD (0)
| [a1] INVOKE (l=12):
| Invoke Ident. : 2ee0 (12000)
| OP: ECMA RO_CALLING_NAME (0)
| [80] Name presentation allowed (l=0)
| IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 7670
| IE:[7d] HLC (l=2) 91 81
| [95] Locking shift. codeset : 5
| IE:[32] EI_PARTY_CATEGORY (l=1) -> ATTENDANT (2)
|______________________________________________________________________________
______________________________________________________________________________
| (304596:000004) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 3 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 80 5e
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 d8 -> [d8] INCOMPATIBLE DESTINATION
|______________________________________________________________________________
Alcatel-Lucent OmniPCX Enterprise
login: mtcl
Password:
Last login: Thu Aug 25 22:43:28 from 130.0.30.56
Alcatel-Lucent OmniPCX Enterprise
standard installation last performed: 02-Apr-2015 02:45:43
# The role of the CPU is MAIN
Application software identity
R11.1-l1.301-37-ae-c0
Business identification: R11.1
Release:
DELIVERY l1.301
Patch identification: 37
Dynamic patch identification: none
Country: ae
Cpu: c0
ACD VERSION
release : 11
bug_fixing : 2
protocol_id : 92
version_dy_hr_stat : 12
t3(1)holidayinn_1> 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 ...
(304551:000001) MTRACER host (130.0.30.10, holidayinn_1), version: R11.1-l1.301-37-ae-c0
(304551:000001) MTRACER num: 019, time: 2016/08/25 22:45:22, loss: 0%
______________________________________________________________________________
| (304596:000002) 1424: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 72 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 5e
| SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a1 83 85 -> T2 : B channel 5 preferred
| IE:[1c] FACILITY (l=26)
| [91] Discriminator of supplementary service applications
| [aa] NFE (l=6):
| [80] Source Entity (l=1) End_PTNX
| [82] Destination Entity (l=1) End_PTNX
| [8b] Interpretation APDU (l=1): DISCARD (0)
| [a1] INVOKE (l=12):
| Invoke Ident. : 2ee0 (12000)
| OP: ECMA RO_CALLING_NAME (0)
| [80] Name presentation allowed (l=0)
| IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 7670
| IE:[7d] HLC (l=2) 91 81
| [95] Locking shift. codeset : 5
| IE:[32] EI_PARTY_CATEGORY (l=1) -> ATTENDANT (2)
|______________________________________________________________________________
______________________________________________________________________________
| (304596:000004) Concatenated-Physical-Event :
| long: 22 desti: 0 source: 0 cryst: 3 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : REL COMP [5a] Call ref : 80 5e
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 d8 -> [d8] INCOMPATIBLE DESTINATION
|______________________________________________________________________________