<div dir="ltr"><div style>Hello,</div><div style><br></div><div style>We're using the B2B module to handle REFERs (as our upstream carriers do not handle REFER). Everything works really well when we follow the examples and when everything is successful. However, if the destination of the REFER (not the provisional_media location, but the actual final destination) responds negatively (say 603 or 404), then we see the following log messages</div>
<div><br></div><div><font face="courier new, monospace">DBG:b2b_logic:b2b_logic_notify_reply: Received a reply [603] while in BRIDGING scenario</font></div><div><font face="courier new, monospace">ERROR:b2b_logic:process_bridge_negreply: unexpected entity_no [2] for tuple [0x7f02af7d5278]</font></div>
<div><font face="courier new, monospace">ERROR:b2b_logic:b2b_logic_notify_reply: Failed to process negative reply while in bridging state</font></div><div><div><br></div><div style>And the other existing call leg appears to get stuck. That is, it'll continue to hear the provisional media until that runs out, and then it'll just be hanging there. I would expect that the other call leg be sent a BYE, which is exactly what happens in this scenario when provisional_media is not used.</div>
<div style><br></div><div style>As far as I can tell, this is a bug in the b2b logic module. I'm happy to try to make a patch and contribute a fix, however, I need a little guidance on what needs to be done (I'm not at all familiar with the internals of this codebase).</div>
<div style><br></div><div style>Thanks for your help,</div><div style>Tolga</div><div><br></div></div><div><br></div></div>