[Asterisk-Dev] iax2 debug format problem?
Rich Adamson
radamson at routers.com
Sat Jun 11 09:05:39 MST 2005
Running cvs-head from yesterday. When receiving an inbound iax call with
debug active, I get the following:
Rx-Frame Retry[ No] -- OSeqno: 002 ISeqno: 004 Type: IAX Subclass: ACK
Timestamp: 01120ms SCall: 00067 DCall: 00007 [208.139.204.228:4569]
Rx-Frame Retry[ No] -- OSeqno: 002 ISeqno: 004 Type: VOICE Subclass: 2
Timestamp: 01420ms SCall: 00067 DCall: 00007 [208.139.204.228:4569]
Tx-Frame Retry[-01] -- OSeqno: 004 ISeqno: 003 Type: IAX Subclass: ACK
Timestamp: 01420ms SCall: 00007 DCall: 00067 [208.139.204.228:4569]
VvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvGvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvRx-Frame Retry[ No] -- OSeqno: 003 ISeqno: 004 Type: DTMF Subclass:
3
Timestamp: 06443ms SCall: 00067 DCall: 00007 [208.139.204.228:4569]
Tx-Frame Retry[-01] -- OSeqno: 004 ISeqno: 004 Type: IAX Subclass: ACK
Timestamp: 06443ms SCall: 00007 DCall: 00067 [208.139.204.228:4569]
vvvvovvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvRx-Frame Retry[ No] -- OSeqno: 004 ISeqno: 004 Type: DTMF
Subclass: 0
Timestamp: 08403ms SCall: 00067 DCall: 00007 [208.139.204.228:4569]
Tx-Frame Retry[-01] -- OSeqno: 004 ISeqno: 005 Type: IAX Subclass: ACK
Timestamp: 08403ms SCall: 00007 DCall: 00067 [208.139.204.228:4569]
vvvovvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvRx-Frame Retry[ No] -- OSeqno: 005 IS
eqno: 004 Type: DTMF Subclass: 0
Timestamp: 09243ms SCall: 00067 DCall: 00007 [208.139.204.228:4569]
Note the frames that include "Type: DTMF" appear to include some junk
that wasn't expected. Should I open a bug tracker problem for this?
(The format problem started several weeks ago actually.) The above was
created by simply dialing a DID number assigned to this box, hitting
the IVR, and keying "300". The IVR works just fine, its just the formating
of the debug output that appears to have a problem.
Rich
More information about the asterisk-dev
mailing list