Hi, I posted a question to this list yesterday because I was having problems with my calls ending as soon as they were bridged. I was originating 2 outbound calls from a lua script, then bridging them. I managed to get round the problem of the calls shutting down immediately by initiating calls using the originate command, thusly:<div>
<br></div><div><div>originate sofia/lpmedia/<a href="mailto:2000@10.15.20.122">2000@10.15.20.122</a> '&lua(click2call_call.lua)'</div></div><div><br></div><div>This causes the lua script to initiate with a session already present and then a bridge to a new call (legB) completes successfully.</div>
<div><br></div><div>Within the lua script I am bridging to leg B like this:</div><div><br></div><div>session:execute("bridge", "[bypass_media_after_bridge=true]sofia/lpmedia/<a href="mailto:91979197@10.15.20.122">91979197@10.15.20.122</a>")</div>
<div><br></div><div>This works, but the reINVITEs which get sent out after legB is established contain the wrong sip request URI.</div><div><br></div><div>- The SIP URI in the reINVITE to Leg A is to the MEDIA IP of leg B (the SIP packet is sent to the correct IP, just the request URI contains the media IP)</div>
<div>- The SIP URI in the reINVITE to Leg B is to the MEDIA IP of leg A... again the SIP packet is sent to the correct IP, it's just the request URI which contains the media IP.</div><div><br></div><div>In some instances the request URI doesn't contain the username either, it is just INVITE sip:<MEDIA_IP></div>
<div><br></div><div>I am using the latest sources of freeswitch from git</div><div><br></div><div>Is this a bug I need to report? It is causing me to receive 404 and 402 errors on the reinvite as the request URI is invalid.</div>
<div><br>Pete</div><div><br></div><div><br></div><div><br></div>