Asterisk versioin: 20.1.0
Other details: 100rel allowed, UPDATE methods allowed.
Call scenario:
A: invite G711
B(remote side): 200
B: re-ninvite with T38 (re-invite crossing Asterisk server)
A: 488 Not Acceptable Here
Here no fall back on the Asterisk side to the G.711a codec (which was a default behavior in older versions < 16.+)
B: sends bye because actually received the 488
Would that be possible to finalize merging this patch?
Not sure why, but the same subject (mentioned by the link above) hadn’t been finalized in the end.
The patch would need to go up on Github under the current contributor license agreement, and based on reading the comments it was not completely correct so someone would have to work on it.
Hello @jcolp , alright, thanks for a clarification.
Is there any way we could continue looking into that?
We are ready to test out any patches. I just need to know which code would be actual for this case (with a fallback to codecs), since I’m not sure that the code (patch) offered by you long time ago (linked by me in the ticket) is still actual. Thank you.
Yes, sorry, my bad. I’ve missed the nick name in the report. Holidays squeezing my head.
We could at least try to test that provided patch, which was actual for the 2019… not sure if this makes much sense. If I confirm it’s working and we can reach out @sioux1977 (patch author), to confirm the contributors license agreement, will that be possible to add this to the master?
ack, let me try to test this out and see what’s coming out of it.
If goes fine, I will go with a pull request.
Please don’t close this ticket, so we have at least some communication point. Thanks.