Hi list,
We are using Kamailio3.1.
The calls are working fine when both UAs are in 3G or different WiFi. However, when both UAs are in LAN (using WiFi) , the call become silent.
What should we do?
Any hint will be great appreciated.
Thank you very much!
Coca
Am 22.08.2011 16:18, schrieb Coca:
Hi list,
We are using Kamailio3.1.
The calls are working fine when both UAs are in 3G or different WiFi. However, when both UAs are in LAN (using WiFi) , the call become silent.
Seems like a NAT problem.
What should we do?
A media relay like rtpproxy is needed, or some application logic to use local IP addresses (ICE).
regards klaus
Dear Klaus,
Thanks for your quick response.(just as you did ever)
I am using rtpproxy. However , in my case , the error was shown as below: ----------------------------------------------------------------------------------
6(32425) INFO: <script>: ALERT: force_rtp_proxy called
6(32425) ERROR: rtpproxy [rtpproxy.c:2211]: incorrect port 0 in reply from rtp proxy
8(32427) INFO: <core> [forward.c:786]: broken reply to forward - no 2nd via
6(32425) ERROR: rtpproxy [rtpproxy.c:2211]: incorrect port 0 in reply from rtp proxy
6(32425) NOTICE: acc [acc.c:275]: ACC: transaction answered: timestamp=1314035733;method=INVITE;from_tag=1499479423;to_tag=1172821397;call_id=415340348;code=200;reason=OK;src_user=123456789;src_domain= mydomain.org;dst_ouser=54321;dst_user=54321;dst_domain=114.158.89.92
7(32426) NOTICE: acc [acc.c:275]: ACC: request acknowledged: timestamp=1314035733;method=ACK;from_tag=1499479423;to_tag=1172821397;call_id=415340348;code=200;reason=OK;src_user=123456789;src_domain= mydomain.org;dst_ouser=54321;dst_user=54321;dst_domain=114.158.89.92
5(32424) INFO: <core> [forward.c:786]: broken reply to forward - no 2nd via
6(32425) NOTICE: acc [acc.c:275]: ACC: transaction answered: timestamp=1314035742;method=BYE;from_tag=1499479423;to_tag=1172821397;call_id=415340348;code=200;reason=OK;src_user=123456789;src_domain= mydomain.org;dst_ouser=54321;dst_user=54321;dst_domain=114.158.89.92
7(32426) INFO: <core> [forward.c:786]: broken reply to forward - no 2nd via
5(32424) INFO: <core> [forward.c:786]: broken reply to forward - no 2nd via
----------------------------------------------------------------------------------
Appreciate any hints. Thanks a lot.
Coca
2011/8/23 Klaus Darilion klaus.mailinglists@pernau.at
Am 22.08.2011 16:18, schrieb Coca:
Hi list,
We are using Kamailio3.1.
The calls are working fine when both UAs are in 3G or different WiFi. However, when both UAs are in LAN (using WiFi) , the call become silent.
Seems like a NAT problem.
What should we do?
A media relay like rtpproxy is needed, or some application logic to use local IP addresses (ICE).
regards klaus
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Am 22.08.2011 20:18, schrieb Coca:
Dear Klaus,
Thanks for your quick response.(just as you did ever)
I am using rtpproxy. However , in my case , the error was shown as below:
6(32425) INFO: <script>: ALERT: force_rtp_proxy called
6(32425) ERROR: rtpproxy [rtpproxy.c:2211]: incorrect port 0 in reply from rtp proxy
Increase loglevel of rtpproxy and watch logging of rtpproxy. Also take a look at the SDP of the processed message - maybe it looks strange.
You can also capture and analyze the communication between Kamailio and rtpproxy by using a UDP socket for communication.
regards Klaus
-
Coca -
Klaus Darilion