Network bind addresses and setting the Via: field

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

 



Just an update to this issue: If I specify the *a_name* of the bind address
in *pjsip_udp_transport_start*, then the Via: header reflects this
correctly, but the SDP still advertises the IP of first interface for
RTP/RTCP (even though I'm not bound to it).

To clarify, the interfaces are on different subnets and the INVITEd party
can't reach my first interface.

I'm sure I probably need to be doing something different after creating the
dialog, like *pjsip_dlg_set_transport*, but I can't quite work out how to do
that. When I use *pjsip_dlg_set_transport* to set the transport to the one
returned by *pjmedia_transport_udp_create*, it seems to invalidate the
dialog (although no error is returned).

What am I missing?

On Thu, Sep 18, 2008 at 2:25 AM, Mark Webster
<mark.webster+pjsip at gmail.com<mark.webster%2Bpjsip at gmail.com>
> wrote:

> Hello again PJSIP people, forgive me if this has already been properly
> discussed or documented elsewhere, but I have searched and not found the
> answer.
>
> My app is running on a linux box with multiple interfaces. I'm not using
> PJSUA, rather just the base PJSIP/MEDIA/etc functions.
>
> What happens is during a SIP dialog, the SDP address and Via: fields are
> always automatically populated with the IP of the first interface. However,
> I am binding to another interface in *pjsip_udp_transport_start*.
>
> Ultimately I will be bridging calls across multiple interfaces, and I need
> a way of directly controlling the IP in the SDP and Via fields for each
> invite dialog.
>
> Could you point me to documentation or a quick example which explains how
> to do this?
>
> Thanks in advance.
> Mark
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080918/bb3cc93f/attachment.html 


[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