Hi, That has been a known issue: https://trac.pjsip.org/repos/ticket/1019, and unfortunately there's no fix for it yet. Best regards, Benny On Tue, May 22, 2012 at 4:27 AM, Gary Metalle <Gary.Metalle at ipfx.com> wrote: > Hi.**** > > ** ** > > Does anyone have an example of using custom transports? I?ve noticed that > pjsip only allows a single TCP transport even if you try to create a new > one for a different local/public address (i.e. a different network > adapter). If you?re using UDP you can create as many *different*transports as you like. > **** > > ** ** > > I?d like to do this so that I can control which network adaptor is being > used for a user account (of which there may be more than one).**** > > ** ** > > I could live with having only one TCP transport at any one point in time > if necessary, but I?ve had trouble with that. There isn?t an API to make > changes to a transport once you?ve created it and I?ve had problems trying > to remove a transport so I can create a new one using:**** > > ** ** > > pjsua_transport_set_enable(transport_id, PJ_FALSE);**** > > pjsua_transport_close(transport_id, PJ_FALSE);**** > > ** ** > > // bla**** > > ** ** > > pjsua_transport_create(required_type, &new_cfg, &transport_id);**** > > ** ** > > To be fair, the documentation does warn against calling > pjsua_transport_close()anyway, but if you don?t call it then you get > problems creating the new transport such as PJSIP_ETYPEEXISTS where the old > one hasn?t been fully removed.**** > > ** ** > > Regards.**** > > ** ** > > *Gary Metalle* > Senior Software Engineer > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20120522/95d69f9d/attachment.html>
