[OpenSIPS-Users] Question about source port on t_relay

[Daniel Goepp]

Yes, you are correct.  I understand that the port in the parameter is the
destination, I just was including exactly what we do.  And yes, what we are
experiencing is just what you say.  We are binding on port 5060 both UDP and
TCP to receive traffic.  Is it possible to force an outbound request on TCP
to have a source port of 5060, instead of just requesting one from the OS?

-dg


On Wed, Aug 18, 2010 at 7:53 AM, Bogdan-Andrei Iancu <bogdan at voice-system.ro
> wrote:

> Hi Daniel,
>
> the param of t_relay() is the destination where to send, not the source.
> In UDP, the source will be all the time one of the defined interfaces,
> but for TPC/TLS, when firing a new connection, the kernel allocates a
> new random port for that - I guess this is the case for you, right ?
>
> Regards,
> Bogdan
>
> Daniel Goepp wrote:
> > We are using:
> >
> > t_relay("tcp:<ip_address>:5060")
> >
> > However this causes the source port to be someone unpredictable.  But
> > if we use UDP, it always comes from 5060 (as we would expect).
> >
> > I'm just looking for some comments on this behavior, and if it is
> > expected or a bug.
> >
> > Thanks
> >
> > -dg
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
>
> --
> Bogdan-Andrei Iancu
> OpenSIPS Bootcamp
> 20 - 24 September 2010, Frankfurt, Germany
> www.voice-system.ro
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100818/ef957fcb/attachment.htm