On 06/23/06 01:22 Andy Brezinsky said the following:
< Protocol Discriminator: Q.931 (8) len=47
< Call Ref: len= 2 (reference 15996/0x3E7C) (Originator)
< Message type: SETUP (5)
> Protocol Discriminator: Q.931 (8) len=10
> Call Ref: len= 2 (reference 48764/0xBE7C) (Terminator)
> Message type: CALL PROCEEDING (2)
> Protocol Discriminator: Q.931 (8) len=14
> Call Ref: len= 2 (reference 48764/0xBE7C) (Terminator)
> Message type: CONNECT (7)
i may be way offbase with this, but on our PRI calls, we usually have
asterisk sending an ALERTING between the CALL PROCEEDING and CONNECT. this
seems borne out by...
< Protocol Discriminator: Q.931 (8) len=9
< Call Ref: len= 2 (reference 15996/0x3E7C) (Originator)
< Message type: RELEASE (77)
< Protocol Discriminator: Q.931 (8) len=13
< Call Ref: len= 2 (reference 15996/0x3E7C) (Originator)
< Message type: STATUS (125)
< [08 03 83 e5 07]
< Cause (len= 5) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0
Location: Transit network (3)
< Ext: 1 Cause: Message not compatible with call state
(101), class = Protocol Error (6) ]
..."Message not compatible with call state" STATUS returned by the other
side. you may want to experiment with a Wait(2) before the Answer().
--
Regards, /\_/\ "All dogs go to heaven."
[EMAIL PROTECTED] (0 0) http://www.openmalaysiablog.com/
+==========================----oOO--(_)--OOo----==========================+
| for a in past present future; do |
| for b in clients employers associates relatives neighbours pets; do |
| echo "The opinions here in no way reflect the opinions of my $a $b." |
| done; done |
+=========================================================================+
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
