Think QSIG-GF TG work as ABC-F

[trjm]

Hi

I have a E1 TG that is configured thusly:
Q931 Signal variant + ABC-F
Remote Network : 10
Trunk COS : 18

Network Routing Table 10 has
Protocol Type + QSIG-GF

From this I would assume that this TG was QSIG-GF, however, I get traces like these
______________________________________________________________________________
| (988495:000007) 1388: Send_IO1 (link-nbr=10, sapi=0, tei=0) :
| long: 365 desti: 0 source: 15 cryst: 0 cpl: 10 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : SETUP [05] Call ref : 10 4d
|
| CONCATENATION OF 2 SEGMENTED MESSAGES
|______________________________________________________________________________
|
| [a1] Sending complete
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a9 83 99 -> T2 : B channel 25 exclusive
| IE:[1c] FACILITY (l=180)
| [9f] 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=48):
| Invoke Ident. : 2ee0 (12000)
| OP: ECMA RO_CALLING_NAME (0)
| [30] Sequence (l=36)
| [80] Name presentation allowed (l=7) 'Bylinje'
| [a6] Sequence of Ecma extension (l=25)
| [30] Sequence (l=23)
| [06] Object id. (l=7) 2b 0c 02 88 52 b6 73
| [30] Sequence (l=12)
| [80] Context specific (l=1) 00
| [81] Context specific (l=7) 42 79 6c 69 6e 6a 65
| [a1] INVOKE (l=93):
| Invoke Ident. : 0001 (1)
| OP: ALCATEL RO_CLASSMARKS (1)
| [30] Sequence (l=80)
| [80] Feature identifier (l=5) 06 44 c0 1f 00
| [82] Cug (l=1) 05
| [83] SubNetwork number (l=1) 00
| [84] Trunk identity (l=1) 34
| [ab] Sequence of Project data (l=62)
| [30] Sequence (l=25)
| OP :RO_CLASSMARKS_SUPPLEMENTARY_INFO_1 (134621715)
| [30] Sequence (l=19)
| [80] Trunk group feature (l=5) 06 00 88 00 00
| [81] Trunk group type (l=1) 06
| [83] Current entity (l=1) 00
| [84] Initial kind of call (l=1) 11
| [85] Context specific (l=1) 00
| [30] Sequence (l=22)
| OP :RO_SERVER_ACCESS_INFO (134621715)
| [30] Sequence (l=16)
| [80] Language (l=1) 01
| [81] type of set (l=1) 00
| [84] Feature identifier 2 (l=5) 00 c0 21 00 54
| [86] Priority of call (l=1) 00
| [30] Sequence (l=9)
| OP :RO_AUTOMATED_ATTENDANT (134621715)
| [30] Sequence (l=3)
| [80] Context specific (l=1) 00
| [a1] INVOKE (l=21):
| Invoke Ident. : 1b9d (7069)
| OP: ALCATEL RO_DIVERTING_LEG_INFO_CSTA (7069)
| [30] Sequence (l=6)
| [82] Initial Called Number (l=4) '1943'
| IE:[1e] PROGRESS_ID (l=2) 80 88
| IE:[27] NOTIF_INDI (l=23)
| 83 : discriminator for notif. extention
| [30] Sequence (l=20)
| OP :ALCATEL CHARGING_INFO (112)
| [30] Sequence (l=10)
| [02] Integer (l=1) 01
| [80] Context specific (l=2) 05 02
| [81] Context specific (l=1) 01
| IE:[27] NOTIF_INDI (l=19)
| 83 : discriminator for notif. extention
| [30] Sequence (l=16)
| OP : 1b77 (7031)
| [30] Sequence (l=5)
| [04] Octet string (l=0)
| [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:[27] NOTIF_INDI (l=31)
| 83 : discriminator for notif. extention
| [30] Sequence (l=28)
| OP : 1b8d (7053)
| [30] Sequence (l=17)
| [02] Integer (l=1) 01
| [02] Integer (l=1) 01
| [30] Sequence (l=9)
| [02] Integer (l=1) 1e
| [02] Integer (l=1) 00
| [02] Integer (l=1) 00
| IE:[6c] CALLING_NUMBER (l=10) -> 21 81 Num : redacted
| IE:[70] CALLED_NUMBER (l=7) -> 80 Num : redacted
| IE:[7d] HLC (l=2) 91 81
| [95] Locking shift. codeset : 5
| IE:[32] EI_PARTY_CATEGORY (l=1) -> UNKNOWN (0)
|______________________________________________________________________________


I suspect this looks a bit like a ABC-F TG. QSIG is also set up as ISO insted of ECMA, and still I see ECMA elements in the trace.
I hope I have not forgot something obvious, but have as far as I can tell created the trunk like the documentation says.

Have I forgotten something?

Rgds
Terje Melberg

[mgoegel]

Thats correct.
OXE sends Alcatel specific vendor informations over QSIG GF trunk. Other side may understand or ignore these additional infos.

Mario

[vad]

Cannot make a test right now, but as I remember what was big difference - calls via seizure prefix or call via Network/Routing number.

[trjm]

Ok. Right now I use speed dial with TG prefix + modified number. Maybe it will help if the speed dial call a routing/network number?

The actual issue is that sometimes the call won't complete and the attendant gets a "bad number" error. I did traces over several days but could not find anything there. I notice that sometimes the number is sent with # (end of dialing character) and sometimes without in the QSIG trace. However, it seems that in most cases the call is set up ok even when # is transmitted.

Anyway, if OXE sends Alcatel-specific info over QSIG-GF then the TG is ok. I'll test with routing/network number and see if that helps.

[mgoegel]

Ok. Right now I use speed dial with TG prefix + modified number. Maybe it will help if the speed dial call a routing/network number?

Yes, try it - last week i had an problem between 2 OXE with a big Siemens node between them (OXE-HICOM-OXE) - calls between OXE nodes was possible, but no call forward or call transfer. After switching from speed dialling to routing numbers, suddenly all problems are gone...

Mario

[trjm]

A small update.

In the beginning...
On the OXE internal numbers a 4 digits, on Avaya 5. All Avaya numbers start with 3.
When OXE call Avaya, Avaya user see name of OXE user. When Avaya user call OXE on the other hand, OXE does not see name of Avaya user. I got Avaya to see OXE name when I switched QSIG from ECMA to ISO, before that no name at all.
So I changed from routing numbers to speed dia by areal so that Avaya names can be entered by hand on OXE. However, this means that there is no room in numbering plan for a routing or network number starting with 3.

The really annoying thing of course if that it mostly works, but every now and again this one number give the OXE attendant a "bad number" error. Next time they try it works again. I am tempted to think that it is something on the Avaya doing this, and think I will have them check Avaya logs when it happens.

[vad]

About name when avay user call OXE user.
1 - name mast be present in t3 trace.
2 - phone feature COS OXE user - Calling name display (CNIP/I-CNAM)=1

[oliveira_Arthur]

I have same problem with IVR. I will try the configuration above.

See the link.

http://web.unitysip.com/CallXpress/Docs ... CX7.71.pdf

[ubhatnagar]

Hello oliveira_Arthur,

I have same issue, but i suggested link is not going through.
Could you please share this document to me at u.bhatnagar@absindia.net

Rgds