A bit update.
When X-Lite(build1101) issue BYE request, 481 response
(Call/Tranasction Does not exist) is returned.
In the case of BudgeTone and WindowsMessengers are OK.
Is this known behavior/bug?
From: - zaki - <zaki(a)zaki.jp>
Date: Fri, 20 Feb 2004 15:13:52 +0900 (JST)
Hi,
I confirmed that rtpproxy release v20040105 can work with sip_router
release rel_0_8_12.
However, BYE request cannot be handled correctly with
sip_router/etc/nathelper.cfg .
I'll check a reason of this issue and will report later again.
Regards,
From: - zaki - <zaki(a)zaki.jp>
Date: Fri, 20 Feb 2004 14:07:28 +0900 (JST)
>
> Hi,
>
> I've tried to use portaone rtpproxy with nathelper, but it looks
> there is interoperability problem.
>
> # export CVSROOT=:pserver:anonymous@cvs.berlios.de:/cvsroot/ser
> # cvs co -r rel_0_8_12 sip_router
> # (cd sip_router; make install)
> # cvs co rtpproxy
> # (cd rtpproxy; ./configure; make install)
> # cp sip_router/etc/nathelper.cfg /usr/local/etc/ser/ser.cfg
>
> After editing ser.cfg to fit my site and starting ser and rtpproxy,
> when I tried to make a call from an endpoint A behind NAT to endpoint
> B behind NAT, signaling was OK(endpoint was ringing), but no media.
>
> In my /var/log/messages, following message appeared.
> "ERROR: send_rtpp_command: can't connect to RTP Proxy"
> So I traced rtpproxy process by "strace -p <rtpproxy's PID> -f
-F",
> then I saw "rtpproxy: command syntax error:" message.
> I think there are no message format compatibility between sip_router
> (branch rel_0_8_12) and rtpproxy(latest).
>
> Should I use another version to work them together?
>
> Regards,
>
> --
> zaki
>