|Anonymous | Login | Signup for a new account||2022-09-26 22:31 EEST|
|Main | My View | View Issues | Change Log | Roadmap | Docs|
|Viewing Issue Simple Details|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0000443||[Yate - Yet Another Telephony Engine] module||major||always||2022-09-11 14:19||2022-09-11 15:14|
|Summary||0000443: IAX2 stalls on calls with unknown IEs|
If an IAX2 call is received with unknown information elements, the call will stall and be rejected (congested on the originating side).
This is incorrect and the correct behavior of IAX2 with unknown IEs is to ignore the IEs, not drop the call because of them. The IAX2 protocol is constantly updated so not doing so would result in mass breakage and incompatibility between servers.
2022-09-11_11:49:14.087698 <INFO> IAX Frame(6,1) with unknown IE identifier 57 [0x7f950401e210]
2022-09-11_11:49:14.087744 <WARN> IAXIEList::createFromFrame. Frame(6,1) with invalid IE [0x7f950401e210]
Asterisk to Asterisk systems are not affected. The bug here is demonstrated on an Asterisk to Yate call.
Yate needs to be updated to ignore rather than reject these unknown IEs.
|Tags||No tags attached.|
|So upon further debugging, it appears this issue may actual be due to Yate expecting the encryption IE is 1 byte, as stated in the RFC. However, it appears to actually be 2 bytes in Asterisk, so the RFC is wrong here, and Yate should follow Asterisk's implementation.|
|2022-09-11 14:19||InterLinked||New Issue|
|2022-09-11 15:14||InterLinked||Note Added: 0000637|
|Copyright © 2000 - 2008 Mantis Group|