Re: [reSIProcate-users] Sending on particular transport

[Nauman Sulaiman <nauman762-home@xxxxxxxxxxx>]

In the end I set the transport on the Outbound proxy to TCP, this works. However

I use SetOverrideHostPort on the contact and the transport=tcp param does not

get added to the contact. If I don't use SetOverrideHostPort it does get added.

So how do I add the transport param to the contact when using SetOverrideHostPort

Thanks

---

From: Nauman Sulaiman <nauman762-home@xxxxxxxxxxx>
To: "resiprocate-users@xxxxxxxxxxxxxxx" <resiprocate-users@xxxxxxxxxxxxxxx>
Sent: Friday, 29 June 2012, 9:57
Subject: Re: [reSIProcate-users] Sending on particular transport

Having read through some posts it seems the easiest way is to add TCP to the transport

type of the Via header, but how can I add this so it is added to all outgoing requests

so the transport selector can see this. Using a decorator is too late.

If DNS overrides this I am not too worried but at least it should be the preferred transport to use

if specified in the Via header

---

From: Francis Joanis <francis.joanis@xxxxxxxxx>
To: Nauman Sulaiman <nauman762-home@xxxxxxxxxxx>
Cc: "resiprocate-users@xxxxxxxxxxxxxxx" <resiprocate-users@xxxxxxxxxxxxxxx>
Sent: Friday, 29 June 2012, 2:52
Subject: Re: [reSIProcate-users] Sending on particular transport

Hi,

(see below)

On Thu, Jun 28, 2012 at 5:50 PM, Nauman Sulaiman
<nauman762-home@xxxxxxxxxxx> wrote:
> Hi,
>
> On resip 1.7 I initialise the transports on the stack like this
>
>  profile->addTransport(UDP, sipPort,V4, address);
>  profile->addTransport(TCP, sipPort, V4, address);
>
> where sip port = 5060
>
> How can I choose to send a sip message over TCP as the stack defaults to UDP
> because there is no
> transport=UDP param on the request uri etc
>
> Is there any setting somewhere
>
> Thanks
>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/

You can have a look at this thread:
http://list.resiprocate.org/archive/resiprocate-devel/msg07937.html

I've never tested it, but you could try having 'transport=tcp' in the
Uri passed to setForceTarget. You can also configure a DUM outbound
proxy and put the transport parameter in there, which I've used in the
past (however, this will force all messages to go to that URI).

Hope this helps,
Francis

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/