After spent much effort. I have found that the connectCallee() cannot 
successfully re-invite caller when the caller is in a NATed network. After 
about 30 seconds the caller got kicked out.  If move the caller into a public 
IP and it works. Therefore, the question is how do I make the conference work 
from conf_auth, if the caller is behind NAT? I have tried eveything I could by 
using nathelper and rtp proxy but no luck. 

using sniffer I can see that an ACK message was sending out from the server to 
the private IP of the caller and that certainly won't get into the caller. 
After about 30 seconds the caller send a BYE to the server. From the sems log 
we can also see the following messages:


(22976) DEBUG: parse_sdp_media (AmSdp.cpp:655):
ret=0; next_line=<>
(22976) DEBUG: getCompatiblePayloads (AmSdp.cpp:348):
using global address: 192.168.2.2
(22976) DEBUG: negotiate (AmSession.cpp:255):
remote party supports telephone events (pt=101)
(22976) DEBUG: setRAddr (AmRtpStream.cpp:328): RTP
remote address set to 192.168.2.2:12622
(22976) DEBUG: setLocalPort (AmRtpStream.cpp:162):
local rtp port set to 10002
(22976) DEBUG: init (AmRtpAudio.cpp:135):
AmRtpAudio::init(...)
(22976) DEBUG: acceptAudio (AmSession.cpp:630):
Sending Rtp data to 192.168.2.2/12622
Certainly the message that was composed by sems would never reach caller either.

Suggestions please. Thanks.

--Ling



----- Original Message ----
From: Juha Heinanen <[email protected]>
To: [email protected]
Cc: [email protected]
Sent: Monday, March 9, 2009 1:28:53 PM
Subject: Re: [Sems] How does conf_auth communicte with conference plug-in?

[email protected] writes:

> Thanks for illumination. How do I use sip control rather than
> t_write_unix?

you load sipctrl plugin instead of unixsockctrl plugin and in sems.conf
tell which ip address sems ua listens at.  that makes sems sip user
agent to which your proxy can send sip requests like to any other ua.
you also need to specify, how application is selected.  there must be
documentation in sems sources about this.

-- juha



      
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to