|
Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Atx command and Eicon Diva Server 4BRI
Am 2005.10.20 09:18 schrieb(en) Carlo Farinella:
Mat Allgood wrote:
>
> Sounds like it is one of the ISDN cause codes:
>
> http://www.telos-systems.com/?/techtalk/cause.htm
Seems to be this one
Cause No. 81 – Invalid call reference value
Hello Carlo,
I don't think this 81 you found in the table is really what you are
looking for.
The table on the referenced page seems to have decimal numbers while
this 81 is hex. (There are no numbers with a..f in the table and the
highest number is 127. Looks like 7-bit values.)
Some data have special encoding in the ISDN protocol messages:
[C:1] 6:0107:619 - SIG-X(029) 08 01 01 05 04 03 90 90 A3 18 01 83 1E
02 80 83
6C 05 01 80 37 31 32 70 04 81 37 31 30
^ ^ 7 1 2 ^ 7 1 0
01 80 81
These are the calling and called number as shown below.
Q.931 CR01 SETUP
Bearer Capability 90 90 a3
Channel Id 83
Progress Indicator 80 83
Calling Party Number 01 80 '712'
Called Party Number 81 '710'
[...]
[C:1] 6:0107:736 - D-R(012) 02 83 02 02 08 01 81 45 08 02 81 BB
^ ^
[C:1] 6:0107:736 - D-X(004) 02 83 01 04
[C:1] 6:0107:737 - SIG-R(008) 08 01 81 45 08 02 81 BB
^ ^
Q.931 CR81 DISC
Cause 81 bb '59'
[C:1] 6:0107:738 - EVENT: Call failed in State 'Outgoing call
proceeding'
Q.931 CR81 DISC
Cause 81 bb '59'
I can find 81 and bb in the hex data. and I assume '59' is a
specifically encoded value because it is written in single quotes like
the calling and called number above.
bb is 80 + 3b (or 3b with highest bit set). 3b hex is 59 decimal.
Maybe the cause number is 59 which is not in the table but seems to be
in section "CLASS 1.3 (service or option not available)"
I found some information on
http://www.eicon.com/support/helpweb/dc9xen/TRACEANA.HTM
Your trace looks similar to Eicon's DiTrace Utility and that's supposed
to write English explanations of the cause codes like this:
17:30:58.589 - SIG-R(008) 08 01 81 45 08 02 81 D8
Q.931 CR8001 DISC
Cause 81 d8 'Incompatible destination'
I think now it's sure the table of cause codes is decimal:
d8 = 80 + 58 ; 58 hex = 88 decimal
The table says "Cause No. 88 - Incompatible destination"
17:30:58.589 - SIG-R(026) 08 01 81 45 08 02 80 91 28 10 2A 41 41 2A
4E 55 4D 42 45 52 20 42 55 53 59 23
Q.931 CR0001 DISC
Cause 80 91 'Number Busy'
Display 2a 41 41 2a ….. 23 "*AA* NUMBER BUSY#"
91 = 80 + 11 ; 11 hex = 17 decimal
Cause No. 17 - Busy, try again later (User busy)
'59' seems to be a value which even Eicon's software doesn't know.
Maybe you should check the docs of your PBX or ask the manufacturer.
There are more hints on this page:
http://www.eicon.com/support/helpweb/dc9xen/ditrqg.htm
STEP 6. If the cause of a "DISCON" is not obvious, then check the
SETUP message
Make sure that the ISDN numbers are correct, and also that the Bearer
Capabilities look right.
In your trace the Setup message contains "Bearer Capability 90 90 a3"
which means Fax Group 3.
This may be a difference to your ISDN phone. The phone probably sends
80 90 A3 Voice call (A-Law voice encoding) or
80 90 A2 Voice call (mu-Law voice encoding - applicable to North
America)
I sometimes had problems with wrong PBX configurations. When fax
machine A is connected to an extension defined as "phone" and fax
machine B connected to a "fax" extension, calls from A to B or vice
versa may get an "incompatible destination" message with a busy tone.
Maybe you can configure the fax extension as "multifunction device" (=
fax+phone combination) or configure your ISDN card not to mark it's
calls as ISDN fax service.
Bodo
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
