PJMedia socket reuse

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

 



Hi Ciro,

havent dont it yey, but did you try to create and the sockets yourself
and do pjmedia_transport_udp_attach instead of create? This way you
should have more control over the socket options

Regards,

Harry

Am 10.01.2016 um 00:22 schrieb Ars Comm - Ciro Ferraiuolo:
> Hi all, I'm using pjmedia to stream rtp traffic between a server and
> some clients.
> The server is behind NAT and firewall and I only can have a couple of
> ports forwarded to its address, so all the clients will stream rtp
> traffic to the server public ip address:ports.
> So I try to call pjmedia_transport_upd_create3 to create a transport for
> each stream to each client, but the api hangs, i guess because I've
> tried to reuse the socket.
> Then I've edited the udp_transport.c file calling the setsockoption with
> the option SO_REUSEADDR after the socket is created.
> It works, but I'm not sure if this is the correct approach. Is there a
> way to accomplish the same goal (receive all the streams on the same
> ipaddress:port) without editing the api?
> 
> Thanks, Ciro.
> -- 
> 
>   *
> CIRO FERRAIUOLO  *
> /Software Engineer/
> E-mail: c.ferraiuolo at arscomm.it <mailto:c.ferraiuolo at arscomm.it> 
> 
> 
> 
> Ars Comm S.r.l.
> Via G. Conti, 8/b - 60131 Ancona (sede legale e operativa)
> Tel: +39 071 2901256 <tel:%2B39%20071%202901256> Fax: +39 071 2910909
> <tel:%2B39%20071%202910909>
> Web: http://www.arscomm.it
> 
> 
> 
> ------------------------------------------------------------------------------------------------------------------------
> RISERVATEZZA
> Questo messaggio da intendersi esclusivamente ad uso del destinatario e
> potrebbe contenere informazioni che sono di natura privilegiata,
> confidenziale o non divulgabile secondo le leggi vigenti. Se il lettore
> del presente messaggio non il destinatario designato, o il
> dipendente/agente responsabile per la consegna del messaggio al
> destinatario designato, si informa che ogni disseminazione,
> distribuzione o copiatura di questa comunicazione strettamente proibita
> e potrebbe essere illegale. Se avete ricevuto questo messaggio per
> errore, vi preghiamo di notificarcelo immediatamente a mezzo e-mail di
> risposta e successivamente di procedere alla cancellazione di questa
> e-mail e relativi allegati dal vostro sistema. Gli allegati al messaggio
> sono stati verificati per i virus, ma si invita il destinatario a tenere
> esclusivamente in considerazione i propri antivirus e le procedure
> relative.
> 
> CONFIDENTIALITY NOTICE
> This message is intended only for the use of the addressee and may
> contain information that is privileged, confidential and exempt from
> disclosure under applicable law. If the reader of this message is not
> the intended recipient, or the employee or agent responsible for
> delivering the message to the intended recipient, you are hereby
> notified that any dissemination, distribution or copying of this
> communication is strictly prohibited and may be unlawful. If you have
> received this e-mail in error, please notify us immediately by return
> e-mail and delete this message and all attachments from your system. Any
> attachments to this message have been checked for viruses, but please
> rely on your own virus checker and procedures.
> ------------------------------------------------------------------------------------------------------------------------
> 
>  
> 
> 
> 
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
> 
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
> 



[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