[OpenSIPS-Users] OpenSIPS 1.8.0-1 with B2BUA/top hiding and UPDATE dialog hiccups
bogdan at opensips.org
Mon Oct 29 12:53:18 CET 2012
The trace looks quite ok , nothing wrong on the first sight .
Is there any possibility to run opensips with debug 6 for the just a
call - I would like to see the logs corresponding to the UPDATE processing.
You can change log level at runtime via the MI "debug" function:
opensipsctl fifo debug 6
and to restore to default:
opensipsctl fifo debug
OpenSIPS Founder and Developer
On 10/26/2012 06:51 PM, Jock McKechnie wrote:
> You betcha;
> Call flow as follows:
> dme at 192.168.0.23, an xlite softphone, calls +186611111111 to our public
> OpenSIPS B2BUA at xxxxxxxxxxx.
> The B2BUA forwards the call onto our mediaproxy, which bridges
> public/private networks, at xxxxxxxxxx.
> The mediaproxy then passes the call to a Dialogic device, at xxxxxxxxx.
> The mediaproxy attempts to utilise an UPDATE to refresh the session
> timer, which is passed back to the mediaproxy, which is passed on to
> the B2BUA, which circles it internally (I presume) until it generates
> a 513 Too Big message and the call tears down (I nipped the end of the
> trap off, so you just see the outgoing BYE).
> Thanks, Bogdan;
> - Jock
> On Thu, Oct 25, 2012 at 6:00 AM, Bogdan-Andrei Iancu
> <bogdan at opensips.org> wrote:
>> Hello Jock,
>> You mean -
>> Also, could you post somewhere you trace (taken on opensips side) ?
>> Thanks and regards,
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developer
>> On 10/22/2012 05:41 PM, Jock McKechnie wrote:
>>> I have a problem with a very simple OpenSIPS doing B2BUA topology
>>> hiding that is unable to handle incoming UPDATEs from the server-side.
>>> The proxy does not tie the UPDATE to the in-progress dialog, and so it
>>> warns with a "No dialog found" error.
>>> I was able to locate a post from earlier this year (March, I think)
>>> with this same issue, and one of the devs patched the daily to correct
>>> it. I'm running the latest 1.8.0-1 from the opensips Debian package
>>> repository and it does not appear to be patched with this fix.
>>> Unfortunately I can't find the post again to determine when the patch
>>> was actually made and to what revision.
>>> Did the patch go in and this feature was broken again, is the patch
>>> not in this release, or am I just stupid?
>>> My thanks!
>>> - Jock
>>> Users mailing list
>>> Users at lists.opensips.org
More information about the Users