I am not sure if this is an Asteriks problem or A2billing, but callback does not work on PRI ZAP channels. More specifically when the Asteriks is connected via PRI to a switch, and the call needs to go out through an ISUP trunk, the call fails, meaning it is rejected by the far away switch where regular calling card calls go through fine.
When compared a regular calling card call to a callback call, we have found a difference between the 2 calls in the messages that are send from the Asterisk box.
We have made 2 seperate calls, which I call the BAD and the GOOD call. The BAD one is using CallBack feature, and the GOOD one is using a calling card to call the same number. The difference between the two setup messages on the D channel is that the BAD call does not have any LAYER-1 information which obviously very important for a call that needs to go through on digital voice channels.
The 2 setup messages coming from PRI are below:
36 30 33 33 31 35 37 33 37 37 = dialed number
36 30 33 37 30 33 30 38 38 38 = calling party number
BAD CALL:
PRIL205-1 Rcvd Msg: c2c500 0 0 0 0 0 37 0 1 8a c2 8 2 7 d6
5 4 2 88 90
18 3 a9 83 97 1e 2 80 83 6c c 21 81
36 30 33 37 30 33 30 38 38 38 70 b a1 36 30 33 33 31 35 37 33 37 37
GOOD CALL:
PRIL205-1 Rcvd Msg: c2c364 0 0 0 0 0 38 0 1 92 ce 8 2 7 d7
5 4 3 80 90 a2
18 3 a9 83 97 1e 2 80 83 6c c 21 80
36 30 33 37 30 33 30 38 38 38 70 b a1 36 30 33 33 31 35 37 33 37 37
5 = indicates a setup message
GOOD CALL:
4 3 80 90 a2
4 = Bearer Capability
3 = Length ...3 bites
80 = Info Transfer Capability...80 = speech
90 = Transfer Mode Rate...always = 90
a2 = User Info Layer1 Protocol...a2 = user info layer 1 ulaw
BAD CALL:
4 2 88 90
4 = Bearer Capability
2 = Length ...2 bites
88 = Unrestricted
90 = Transfer Mode Rate...always = 90
There is no user info layer 1 information
So if anybody knows how to fix this in A2B or Asterisk, please share.
Cent
|