Different scenario of Call flow in QSIG

Post Reply
HUSSAINQCS

Different scenario of Call flow in QSIG

Post by HUSSAINQCS »

OXE (Hotel-A)and Avaya(Hotel-B) are going to link by QSIG(E1)


Avaya admin user (7506)

From OXE room user(7101)is calling to Avaya operator console

OXE user wants prefix 9 to call the avaya console

In OXE I configured QSIG-BC trunk group(20) and i have created prof.trunk group prefix(9)


Can anybody explain how the call flow will work and whether oxe user name is able to display in Avaya console in QSIG-BC

When oxe room user wants to call to Avaya console with the prefix "9" Or it is necessary to create any routing prefix?


To call Avaya admin user from the oxe we have to just dial the trunk prefix and dial the no of avaya user (7506) or any specific settings to be done ?
HUSSAINQCS

Re: Different scenario of Call flow in QSIG

Post by HUSSAINQCS »

Calls not establishing from oxe to avaya but avaya to oxe they can able to call

From OXE side from ext 3670 i was using prefix 20 to seize the qsig trunk after that i dial remote PABX extension no 7670 calls not able to establish


Traces Analyser activated

mtracer started ...
(867090:000001) MTRACER host (130.0.30.10, holidayinn_1), version: R11.1-l1.301-37-ae-c0
(867090:000001) MTRACER num: 023, time: 2016/08/24 02:48:43, loss: 0%
______________________________________________________________________________
| (867176:000002) 1569: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 263 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 49
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a1 83 98 -> T2 : B channel 24 preferred
| IE:[1c] FACILITY (l=123)
| [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=38):
| Invoke Ident. : 2ee0 (12000)
| OP: ECMA RO_CALLING_NAME (0)
| [30] Sequence (l=26)
| [80] Name presentation allowed (l=2) 'IT'
| [a6] Sequence of Ecma extension (l=20)
| [30] Sequence (l=18)
| [06] Object id. (l=7) 2b 0c 02 88 52 b6 73
| [30] Sequence (l=7)
| [80] Context specific (l=1) 00
| [81] Context specific (l=2) 49 54
| [a1] INVOKE (l=69):
| Invoke Ident. : 0001 (1)
| OP: ALCATEL RO_CLASSMARKS (1)
| [30] Sequence (l=56)
| [80] Feature identifier (l=5) 06 44 4f 1f 04
| [82] Cug (l=1) 00
| [83] SubNetwork number (l=1) 00
| [ab] Sequence of Project data (l=41)
| [30] Sequence (l=15)
| OP :RO_CLASSMARKS_SUPPLEMENTARY_INFO_1 (134624083)
| [30] Sequence (l=9)
| [83] Current entity (l=1) 01
| [84] Initial kind of call (l=1) 11
| [85] Context specific (l=1) 01
| [30] Sequence (l=22)
| OP :RO_SERVER_ACCESS_INFO (134624083)
| [30] Sequence (l=16)
| [80] Language (l=1) 01
| [81] type of set (l=1) 05
| [84] Feature identifier 2 (l=5) 00 c0 20 00 56
| [86] Priority of call (l=1) 00
| IE:[27] NOTIF_INDI (l=44)
| 83 : discriminator for notif. extention
| [30] Sequence (l=41)
| OP :ALCATEL CHARGING_INFO (112)
| [30] Sequence (l=31)
| [12] Numeric string (l=4) 33 36 37 30
| [80] Context specific (l=2) 05 00
| [81] Context specific (l=1) 01
| [82] Context specific (l=10) 20 20 20 20 20 20 20 20 20
| 20
| [86] Context specific (l=1) 01
| [87] Context specific (l=1) 00
| IE:[27] NOTIF_INDI (l=23)
| 83 : discriminator for notif. extention
| [30] Sequence (l=20)
| OP : 1b77 (7031)
| [30] Sequence (l=9)
| [12] Numeric string (l=4) 33 36 37 30
| [02] Integer (l=1) 01
| IE:[27] NOTIF_INDI (l=14)
| 83 : discriminator for notif. extention
| [30] Sequence (l=11)
| OP : 1b7d (7037)
| [05] ARG NULL (l=0)
| IE:[6c] CALLING_NUMBER (l=6) -> 00 81 Num : 3670
| IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 7671
| IE:[7d] HLC (l=2) 91 81
| [95] Locking shift. codeset : 5
| IE:[32] EI_PARTY_CATEGORY (l=1) -> EXTENSION (1)
|______________________________________________________________________________

______________________________________________________________________________
| (867177:000007) 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 49
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 d8 -> [d8] INCOMPATIBLE DESTINATION
|______________________________________________________________________________

___________________________________________________
HUSSAINQCS

Re: Different scenario of Call flow in QSIG

Post by HUSSAINQCS »

HUSSAINQCS wrote: 04 May 2017 09:39 Calls not establishing from oxe to avaya but avaya to oxe they can able to call

From OXE side from ext 3670 i was using prefix 20 to seize the qsig trunk after that i dial remote PABX extension no 7670 calls not able to establish


Traces Analyser activated

mtracer started ...
(867090:000001) MTRACER host (130.0.30.10, holidayinn_1), version: R11.1-l1.301-37-ae-c0
(867090:000001) MTRACER num: 023, time: 2016/08/24 02:48:43, loss: 0%
______________________________________________________________________________
| (867176:000002) 1569: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 263 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 00 49
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a1 83 98 -> T2 : B channel 24 preferred
| IE:[1c] FACILITY (l=123)
| [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=38):
| Invoke Ident. : 2ee0 (12000)
| OP: ECMA RO_CALLING_NAME (0)
| [30] Sequence (l=26)
| [80] Name presentation allowed (l=2) 'IT'
| [a6] Sequence of Ecma extension (l=20)
| [30] Sequence (l=18)
| [06] Object id. (l=7) 2b 0c 02 88 52 b6 73
| [30] Sequence (l=7)
| [80] Context specific (l=1) 00
| [81] Context specific (l=2) 49 54
| [a1] INVOKE (l=69):
| Invoke Ident. : 0001 (1)
| OP: ALCATEL RO_CLASSMARKS (1)
| [30] Sequence (l=56)
| [80] Feature identifier (l=5) 06 44 4f 1f 04
| [82] Cug (l=1) 00
| [83] SubNetwork number (l=1) 00
| [ab] Sequence of Project data (l=41)
| [30] Sequence (l=15)
| OP :RO_CLASSMARKS_SUPPLEMENTARY_INFO_1 (134624083)
| [30] Sequence (l=9)
| [83] Current entity (l=1) 01
| [84] Initial kind of call (l=1) 11
| [85] Context specific (l=1) 01
| [30] Sequence (l=22)
| OP :RO_SERVER_ACCESS_INFO (134624083)
| [30] Sequence (l=16)
| [80] Language (l=1) 01
| [81] type of set (l=1) 05
| [84] Feature identifier 2 (l=5) 00 c0 20 00 56
| [86] Priority of call (l=1) 00
| IE:[27] NOTIF_INDI (l=44)
| 83 : discriminator for notif. extention
| [30] Sequence (l=41)
| OP :ALCATEL CHARGING_INFO (112)
| [30] Sequence (l=31)
| [12] Numeric string (l=4) 33 36 37 30
| [80] Context specific (l=2) 05 00
| [81] Context specific (l=1) 01
| [82] Context specific (l=10) 20 20 20 20 20 20 20 20 20
| 20
| [86] Context specific (l=1) 01
| [87] Context specific (l=1) 00
| IE:[27] NOTIF_INDI (l=23)
| 83 : discriminator for notif. extention
| [30] Sequence (l=20)
| OP : 1b77 (7031)
| [30] Sequence (l=9)
| [12] Numeric string (l=4) 33 36 37 30
| [02] Integer (l=1) 01
| IE:[27] NOTIF_INDI (l=14)
| 83 : discriminator for notif. extention
| [30] Sequence (l=11)
| OP : 1b7d (7037)
| [05] ARG NULL (l=0)
| IE:[6c] CALLING_NUMBER (l=6) -> 00 81 Num : 3670
| IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 7671
| IE:[7d] HLC (l=2) 91 81
| [95] Locking shift. codeset : 5
| IE:[32] EI_PARTY_CATEGORY (l=1) -> EXTENSION (1)
|______________________________________________________________________________

______________________________________________________________________________
| (867177:000007) 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 49
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 d8 -> [d8] INCOMPATIBLE DESTINATION
|______________________________________________________________________________

___________________________________________________
Sorry posted in wrong forum
User avatar
murraya
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 900
Joined: 16 Oct 2007 02:35

Re: Different scenario of Call flow in QSIG

Post by murraya »

hi just a note....
you say " i dial remote PABX extension no 7670"
trace says " IE:[70] CALLED_NUMBER (l=5) -> 80 Num : 7671"

is 7671 valid?
Best Regards
Murray

ACSE 10.0 corporate
ACSE 6.x IPT data
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3856
Joined: 23 Sep 2004 06:47

Re: Different scenario of Call flow in QSIG

Post by vad »

Problem with any calls to Avaya or only with calls to admin?
HUSSAINQCS

Re: Different scenario of Call flow in QSIG

Post by HUSSAINQCS »

All calls
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3856
Joined: 23 Sep 2004 06:47

Re: Different scenario of Call flow in QSIG

Post by vad »

You need to ask Avaya - why Avaya send "INCOMPATIBLE DESTINATION"
HUSSAINQCS

Re: Different scenario of Call flow in QSIG

Post by HUSSAINQCS »

Thanks all for support

Calls established from OXE to avaya after made changes in system parameter a law to u law conversion parameter from false to true
Post Reply

Return to “Trunk Groups”