pjsip client always populates itself as "controlled" agent in stun connectivity checks for the incoming ice-lite call

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Oct 15, 2009 at 11:16 AM, amaresh marekar <amaresh.dm at gmail.com> wrote:
> Hi
>
> I am doing an inter-op ice feature testing of pjsip client with the other
> client which supports only ice-lite feature , for incoming ice-lite call
> scenario pjsip client sends the stun connectivity checks to remote candidate
> as "controlled" agent instead of "controlling" adent , As per the draft-19
> is if the peer is ice-lite then the pjsip client should always be the
> "controlling" agent irrespective of incoming or outgoing call . Please let
> me know how to go about this and has any once face similar issue in this
> group? .
>

Can you post the SDP as sent by the ice-lite agent?

Thanks
 Benny



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux