Hi Gonzalo,

Thanks a lot for your reply. I took a closer look at the issue and I guess we 
figured out the reason why this is happening. But, still couldnt get the 
solution unfortunately.  Our topology is like this:

sipml5(behind NAT) -> (Public Interface)kamailio(Private Interface) <---->  
Freeswitch

So, when we are sending calls to to freeswitch via Kamailio; Freeswitch is 
updating the SDP with its private IP. Therefore the client tries to send RTPs 
to the private IP of freeswitch. We have rtpproxy installed in our Kamailio 
server. We tried bunch of stuffs to solve the issue like ICE handling with 
rtpengine but nothing worked out.  Can you please give me some more advise that 
I may try ?

Thanks in advanced.



Date: Wed, 22 Oct 2014 09:53:58 -0700
Subject: Re: [SR-Users] One sided or no voice issue with websockets
From: gascagonz...@gmail.com
To: sr-users@lists.sip-router.org
CC: do...@live.com

Hi Kamrul,
Can you provide more details about the call flow:It is important to understand 
the following:-Topology-Web browser models and versions (Chrome vs 
FireFox)-Kamailio version
When you say:"It works perfectly within local network"
Please take a look at ICE negotiation.
I have sipml5 placing calls to Asterisk via Kamilio working without any issues.
sipml5 ---> kamailio --> fs --> asterisk    ------------------ media 
------------>
Please provide logs:sipml5 (java console)kamailio logs(If possible browser logs)
-Gonzalo

On Wed, Oct 22, 2014 at 9:12 AM, Amit Patkar <a...@avhan.com> wrote:
Please check ICE server settings. Your browser may be publishing local IP. One 
way voice or no voice is typical case when client is behind firewall.

Regards,
Amit Patkar

dodul <do...@live.com> wrote:


Hi



I didn't get any responses from anyone regarding my issue.  Can someone please 
give me some clue what I can do? Or if more information is needed please let  
know so that I can provide.  







Sent from my Samsung Galaxy smartphone.






-------- Original message --------

From: Kamrul Khan <do...@live.com> 

Date:10-21-2014 17:45 (GMT-06:00) 

To: sr-users@lists.sip-router.org 

Cc: 

Subject: [SR-Users] One sided or no voice issue with websockets 





Hi,



We have a setup with sipml5 to kamailio. It works perfectly within local 
network. In public network the signaling establishes perfectly, but most of the 
time we hear no voice, sometimes we hear one sided voice and in rare cases we 
hear voice from both sides.
 To fix this issue we configured our nathandler like the below: But, still no 
luck. Any idea how to fix this? Please HELP!!!



modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)")

modparam("nathelper", "nortpproxy_str", "a=sdpmangled:yes\r\n")

.

.

.

route {

.

.

 if (nat_uac_test("115")) {

                if(nat_uac_test("64"))

                    force_rport();

                }

                if (method=="REGISTER") {

                    fix_nated_register();

                    add_rcv_param();

                } else {

                    fix_nated_contact();

                    if(nat_uac_test("64")){

                        if (!add_contact_alias()) {

                            xlog("L_ERR", "Error aliasing contact <$ct>\n");

                            sl_send_reply("400", "Bad Request");

                            exit;

                        }

                    } else {

                        add_rcv_param();

                    }

                }

            }

.

.



onreply_route {

    if (nat_uac_test(64)) {

            add_contact_alias();

        }

.

.

}








_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



                                          
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Reply via email to