Collect calls over ISDN

Go ahead, shoot for the feature requests, and if anyone knows the solution, they will share it with you. If there is a lot of people who request something, I will make a marketing request directly with Alcatel. A good idea would be to create a poll with each request. Alcatel-Lucent is aware of this forum.
Post Reply
oliveira_Arthur
Member
Posts: 143
Joined: 19 Sep 2008 22:27
Location: Brazil

Collect calls over ISDN

Post by oliveira_Arthur »

In Brazil, calls may be paid by called user.
In R2, OXE is ready to Denied or allow collect calls by COS or TrunkGroup.
ISDN still not implemented. Above we can find collect call trace.

______________________________________________________________________________
| (808938:000025) Concatenated-Physical-Event :
| long: 53  desti: 0  source: 0  cryst: 2  cpl: 6  us: 0  term: 0  type a5
| tei: 0  >>>>  message received : SETUP [05]    Call ref :  12 c5
|SENDING COMPLETE
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3)  a1 83 9c -> T2 : B channel 28 preferred
| IE:[4a] UNKNOWN (l=1) 81
| IE:[6c] CALLING_NUMBER (l=12)  ->  21  83  Num : 9191374488
| IE:[70] CALLED_NUMBER (l=5)  ->  c1  Num : 3046
|______________________________________________________________________________

______________________________________________________________________________
| (808938:000026) 1344: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 26  desti: 0  source: 15  cryst: 2  cpl: 6  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : STATUS [7d]    Call ref :  92 c5
|______________________________________________________________________________
|
| IE:[08] CAUSE (l=3) 81 e3 4a -> [e3]
|    INFORMATION ELEMENT NON-EXISTENT OR NOT IMPLEMENTED
| IE:[14] CALL_STATE (l=1) 06
|______________________________________________________________________________

______________________________________________________________________________
| (808938:000027) 1344: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23  desti: 0  source: 15  cryst: 2  cpl: 6  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : CALL PROC (02)  Call ref :  92 c5
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3)  a9 83 9c -> T2 : B channel 28 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (808938:000028) 1344: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22  desti: 0  source: 15  cryst: 2  cpl: 6  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : ALERT (01)  Call ref :  92 c5
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 81 88
|______________________________________________________________________________

______________________________________________________________________________
| (808959:000029) 1344: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 30  desti: 0  source: 15  cryst: 2  cpl: 6  us: 8  term: 0  type a5
| tei: 0  <<<<  message sent : CONNECT (07)  Call ref :  92 c5
|______________________________________________________________________________
|
| IE:[4c] CONNECTED_NUMBER (l=10)  ->  01  81  Num : 33483046
|______________________________________________________________________________
Regards,

Arthur Oliveira
User avatar
alex
Senior Member
Posts: 1457
Joined: 06 Jul 2004 07:27
Contact:

Re: Collect calls over ISDN

Post by alex »

This IE - 4a is used for packet communication (X.25).
For reverse charging feature you provider should send FACILITY IE
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
oliveira_Arthur
Member
Posts: 143
Joined: 19 Sep 2008 22:27
Location: Brazil

Re: Collect calls over ISDN

Post by oliveira_Arthur »

How we can see on Aculab Docs, http://www.pulsewan.com/data101/q931.pdf, 4A = 1001010 is the IE value to Reverse Charging.
The PNC is sending correct code facility. Where on OXE I can change this to Reverse Charge?

Thanks.
Regards,

Arthur Oliveira
User avatar
alex
Senior Member
Posts: 1457
Joined: 06 Jul 2004 07:27
Contact:

Re: Collect calls over ISDN

Post by alex »

oliveira_Arthur wrote:How we can see on Aculab Docs, http://www.pulsewan.com/data101/q931.pdf, 4A = 1001010 is the IE value to Reverse Charging.
The PNC is sending correct code facility. Where on OXE I can change this to Reverse Charge?

Thanks.
Your PNC has a certificate from Aculab that it complies with Q.956? OK. That means they have kind of special standards comparing to the rest of the world.
Read the Q.931. It is written there - IE 4a is for packet X.25 packet communication, not for the channel communication.
If you want "reverse charging" feature (ITU style), ALU (as any telecom manufacturer) would be kind enough to ask your provider to comply with Q.956. :lol:
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
Post Reply

Return to “Feature Request”