Hi there Kaeman,
first of all in the case of checking calls to registered behind nat
users, you should check branch flags and not global ones.
Regarding your question, if you have a problem, please send us the
logs if SIP Messages (ngrep -t -W byline port 5060), the proper
description and the configuration used.
Cheers,
DanB
On 8/31/07, Kaeman Chris <[EMAIL PROTECTED]> wrote:
>
> Hello Dan/Openser Users,
>
> As described below i solved the problem of handling media.
>
> I think the problem was, as the configuration i did previously was between
> the UAs behind NAT and the proxy server. Now i made some changes to the
> configuration that the GWs with Public IP is sending the calls to Openser
> Server.
>
> The change made was to the on_reply_route[x]
>
> before it was(which was not handling media):
>
> onreply_route[1] {
>
> if ((isflagset(6) || isflagset(7)) &&
> (status=~"(180)|(183)|2[0-9][0-9]")) {
>
> after it is(which is handling media):
>
> if ((isflagset(6) || isflagset(7)) ||
> (status=~"(180)|(183)|2[0-9][0-9]")) {
>
> Due to && operator i was checking both the conditions and this was making
> the call exiting without getting to the Media(use_media_proxy();) which with
> the || operator is making it to reach the media.
>
> Please can anyone check am i doing correct is this going to affect anywhere
> else on the processing the SIP Messages; because i am facing some problem
> with the SIP Messages after the call is answered i.e. at the 183, where in
> the Supplier Supplier IP is exchanged with the customer ip:(.
>
> Please let me know;
>
> Thanks!!
>
> Regards,
> KChris.
> Dan-Cristian Bogos <[EMAIL PROTECTED]> wrote:
> Hi Kaeman,
>
> as per the logs you have sent me (please in the future keep
> users@openser.org on cc so others can use also the results of our time
> invested work), it looks like you are not handing properly the RTP
> part.
>
> You have a combination between proxy and non proxy of RTP. If you
> check your packets you will see that for the case of INVITE from
> RemoteProxy1-> OpenSER -> RemoteProxy2, you will rewrite the
> connection IP with the OpenSER IP Address (RTP Sockets) so the
> RemoteProxy2 will think that he must speak with OpenSER, but for the
> case of 183 replied back (200 OK, same case) you will not rewrite the
> connection IP, and the RemoteProxy1 - call originator, will have the
> feeling that he must send the RTP packets directly to RemoteProxy2.
> Therefore you must decide the scenario you want: proxy all through
> your openser (rtpproxy) or proxy nothing and let the parties speak
> directly to each other and have only signaling passing through your
> openser server.
> Since you don't have a NAT case here, I thing it should be pretty easy
> to do the correct setup.
>
> Hope you did get my point.
>
> Cheers,
> DanB
>
> On 8/30/07, Kaeman Chris wrote:
> >
> > Hi Daniel,
> >
> > I agree with you:). thanks for your reply. I see life in me NOW.
> >
> > Ok, find the debug with ngrep. I did that grepping the port 5060. Is that
> > OK? Let me know if you need with any specific keyword.
> >
> > Attached you will find the debug file. Thanks!!
> >
> > Regards,
> > KChris.
> >
>
>
>
> ________________________________
> DELETE button is history. Unlimited mail storage is just a click away.
>
>
_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
