[BUG]After receiving 183 and then receiving UPDATE, sbc can only implement single-pass problems

[westice007]

Describe the bug
If there is no 183, INVITE is directly collected, and the call is normal.
However, when has 183, and the peer end sends the INVITE instead of the UPDATE message, the ringing number of 183 can be heard, and the peer end can hear my voice, but I cannot hear the voice of the peer party, and no RTP data from the peer party to the sbc can be queried

It seems that the sbc did not process and forward the UPDATE instruction

[hnimminh]

@westice007 could you please send me pcap file?