[Blink] wrong request uri

[Adrian Georgescu]

Juha,

This seem to happen automatically in the underlying PJSIP library. I am wondering if this is correct behavior or not.

Anyway what should the next hop do with this request URI? Should it use the transport parameter from it for routing to the next hop or should it lookup the remote domain in NAPTR record to figure out the transport?

Any idea what is the correct behavior for the next hop receiving this RURI?

Adrian


On Oct 1, 2010, at 11:24 PM, Adrian Georgescu wrote:

> Seems to be a bug. We will check this.
> 
> Adrian
> 
> 
> On Oct 1, 2010, at 9:59 PM, Juha Heinanen wrote:
> 
>> i added ;transport=tcp to outbound_proxy and as result blink
>> constructed this kind of request uri when i called 4444 at sip2sip.info:
>> 
>> INVITE sip:4444 at sip2sip.info;transport=tcp
>> 
>> it is plain wrong.  blink should not mess around with whatever user
>> writes as request uri.  if outbound_proxy has a particular transport
>> protocol, blink should use that to reach outbound proxy and leave
>> request uri as is.  now i cannot call sip:4444 at sip2sipinfo at all
>> because that domain does not support tcp.
>> 
>> -- juha
>> _______________________________________________
>> Blink mailing list
>> Blink at lists.ag-projects.com
>> http://lists.ag-projects.com/mailman/listinfo/blink
>> 
> 
> _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
>