[Asterisk-Dev] hangupcause - tracethrough from PRI

[Mark Edwards]

Hi.

I am hopeful that I might be able to engage someones assistance in a testing
and debugging effort.

I have a configuration thus:

PRI ==> ASTERISK (CVS-D2005.05.19) ==> IAX2 ==> ASTERISK (CVS-HEAD) ==> AMI
==> Dialer application

The Dialer relies on knowing why a call was hung up. Unfortunately, I am not
seeing much useful information appearing in the IAX2 inbound stream.

Inter-Asterisk eXchange v2
Packet type: Full packet (1)
.000 0000 0000 1110 = Source call: 14
.000 0000 0000 0010 = Destination call: 2
0... .... .... .... = Retransmission: False
Timestamp: 1258
Outbound seq.no <http://seq.no>.: 4
Inbound seq.no <http://seq.no>.: 3
Type: IAX (6)
IAX type: HANGUP (5)
Information Element: Hangup cause (0x2A)
IE id: Hangup cause (0x2A)
Length: 1
Hangup cause: Unknown (0x00)

is the output from Ethereal.

Evidently, the channel->hangupcause is not being set.

I have traced through various parts of channel.c, chan_zap.c and chan_iax2.c
and can see various places where the hangupcause appears to get set, but
without a PRI to test with, I am somewhat stumped.

This is a bit of a showstopper for me unfortunately and I would be very
grateful if someone could assist me with finding the reason why this
hangupcause isn't being set by chan_zap.c and the value finding its way back
into the IAX2 packet.

I am starting to form an opinion that this might be a mismatch between
versions of Asterisk and would be grateful if someone could assist me in my
investigations by helping me understand the typical sequence of events in a
PRI and in chan_zap.c when an Unobtainable or Busy number is called. This
would greatly help me determine if for some reason the hangupcause is not
being set by chan_zap in the asterisk channel structure.

cheers,

Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20050918/0d560062/attachment.htm