Alcatel Unleashed

Hello everyone,
I have problem with transit call on client.
My client does not have unique numbers for users, it is necessary to use ARS on Alcatel to perform the dialing for other equipment.
The dialing pattern in ALCATEL is ARS prefix + 6 number

[Topology.]
NEC ---ISDN---> OXE(1) ---SIP---> PANASONIC/ASTERISK/OXE(2)


[Calls scenario]
OXE(1) > ALL - OK
ALL > OXE(1) - OK
ALL > OXE(1) > NEC - OK
NEC > OXE(1) > ALL -NOK

1.Ext 4067(NEC) call to all other user 9924.

2.OXE(1) receive the number 619924 translate to format AC619924(ARS prefix+number) and the call is DISCONNECT.

I tried to translate it to an abbreviated(#*61) one which in turn dialed AC619924 and the call is DISCONNECT again.


[ISDN log]
______________________________________________________________________________
| (722617:000023:05023) Concatenated-Physical-Event :
| long: 45 desti: 0 source: 0 cryst: 3 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 6d 00
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 90 90 a3
| IE:[18] CHANNEL (l=3) a9 83 94 -> T2 : B channel 20 exclusive
| IE:[6c] CALLING_NUMBER (l=5) -> 80 Num : 4067
| IE:[70] CALLED_NUMBER (l=7) -> 80 Num : 619924
| [a1] Sending complete
|______________________________________________________________________________

______________________________________________________________________________
| (722617:000024:04994) 4994: Send_IO1 (link-nbr=2, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : ed 00
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 94 -> T2 : B channel 20 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (722618:000025:04994) 4994: Send_IO1 (link-nbr=2, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : DISCONNECT [45] Call ref : ed 00
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

______________________________________________________________________________
| (722619:000026:05023) Concatenated-Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 3 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : 6d 00
|______________________________________________________________________________

______________________________________________________________________________
| (722619:000027:04994) 4994: Send_IO1 (link-nbr=2, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : ed 00
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

[SIP log]
no call appears when the NEC user dials


Thanks and regards!

Some problem with ARS management.
F.e. - in ARS prefix you have logical discriminator - Discrimiminator selector managed in ISDN TG Entity (not in user Entity)?

Without ARS management explanation - not easy to help.

vad wrote: ↑21 Oct 2020 01:06 Some problem with ARS management.
F.e. - in ARS prefix you have logical discriminator - Discrimiminator selector managed in ISDN TG Entity (not in user Entity)?

Without ARS management explanation - not easy to help.

- The DID table translates the number received XXXXXX to ACXXXXXX.
- AC is the prefix ARS - Type: ARS Prof.Trk Grp Seiz.with overlap - Discriminator Nr. : 6
- ISDN TG Entity is 0, this Entity have Discrimiminator 06 : 199
- The Numbering Discriminator 199 has different dialing rules using ARS Route List Number for each destination.
- Analyzing the ARS Route List Number 61 (example), it has "Trunk Group: 903" and "Numbering Command Tabl.ID: 161"
- The TG 903 is T2-SIP/ISDN.
- The Command Table 161 have - Carrier Reference : 0 - Command : I - Associated SIP gateway : 161

Strange is that nothing appears in the SIP trace, that is, it was unable to use the ARS prefix but in the opposite direction it works normal.

Check with lookars (may be time-based route list not managed) or route call to internal number.
F.e. in route list 61 manage for test - TG id=-1 (internal route), delete 6, add XXXX (some internal number).
If call will be routed to internal number XXXX - with management Ok up to route list.

- lookars is OK
- I change the route list 61 for internal route but not work

[T3 log]
______________________________________________________________________________
| (304477:000023:05023) Concatenated-Physical-Event :
| long: 45 desti: 0 source: 0 cryst: 3 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 23 04
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 90 90 a3
| IE:[18] CHANNEL (l=3) a9 83 91 -> T2 : B channel 17 exclusive
| IE:[6c] CALLING_NUMBER (l=5) -> 80 Num : 4067
| IE:[70] CALLED_NUMBER (l=7) -> 80 Num : 619924
| [a1] Sending complete
|______________________________________________________________________________

______________________________________________________________________________
| (304477:000024:04992) 4992: Send_IO1 (link-nbr=2, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : a3 04
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 91 -> T2 : B channel 17 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (304477:000025:04992) 4992: Send_IO1 (link-nbr=2, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : DISCONNECT [45] Call ref : a3 04
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 9b -> [9b] DESTINATION OUT OF ORDER
|______________________________________________________________________________

______________________________________________________________________________
| (304478:000026:05023) Concatenated-Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 3 cpl: 6 us: 0 term: 0 type a5
| tei: 0 >>>> message received : RELEASE [4d] Call ref : 23 04
|______________________________________________________________________________

______________________________________________________________________________
| (304478:000027:04992) 4992: Send_IO1 (link-nbr=2, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 3 cpl: 6 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : REL COMP [5a] Call ref : a3 04
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=2) 81 90 -> [90] NORMAL CALL CLEARING
|______________________________________________________________________________

is transit authorised between # trkgp isdn and sip ?

As I understand:
- OXE1 - ALL works Ok via ARS.
- calls from NEC to ALL - you rout via same ARS (prefix and route).

In this case you have only two point:
- discriminator selector (for ARS prefix) you need to manage in ISDN TG Entity.
- connection COS (ISDN TG connection COS --> SIP TG connection COS) must allow transit connection.

Haroun and Vad,
some information of the trunks:
ISDN
Entity: 0
Public Network Category: 31
Connection Category ID: 5
Trunk category ID: 19
ARS class of service: 31

SIP
Entity: 0
Public Network Category: 31
Connection Category ID: 0
Trunk category ID: 31
ARS class of service: 31

======================
Connection Category 0 or 5 - allows all.
Transfer Category 0, 5 or 31 - allows all.
Private Category 0, 5 or 31 - allows all.

OXE(1) > ALL - OK
You use ARS or Network/routing prefixes for this?

NEC > OXE(1) > ALL -NOK
For calls you use THE SAME way as for OXE(1) user calls to ALL?

vad wrote: ↑01 Nov 2020 23:09 OXE(1) > ALL - OK
You use ARS or Network/routing prefixes for this?

ARS

vad wrote: ↑01 Nov 2020 23:09 NEC > OXE(1) > ALL -NOK
For calls you use THE SAME way as for OXE(1) user calls to ALL?

Yes, same way.