[Blink] transport problem persists
Adrian Georgescu
ag at ag-projects.com
Fri Dec 17 14:27:13 CET 2010
OK, got it now, thanks.
On Dec 17, 2010, at 2:25 PM, Juha Heinanen wrote:
> Adrian Georgescu writes:
>
>>> i reported a month or so back that blink adds transport protocol
>>> to request uri based on what it uses for its outbound proxy. for
>>> example it sends this kind of request uri when i try to place call
>>> tosip:3333 at sip2sip.info:
>>>
>
>>>
>>> the reply that i got was that it is a bug in pjsip library. when i
>>> checked pjsip pages, i noticed that blink is using a pretty old version
>>> of that library. perhaps the bug is fixed in later versions?
>>>
>>> this bug quite serious, since it makes other outbound proxy transports
>>> than udp pretty much useless.
>>
>> I am not sure what you mean. Can you please rephrase it?
>
> adrian,
>
> sorry if my wording was not clear. i have noticed that if i have
> Outbound Proxy defined on Server Settings page and Transport value TCP
> or TLS and then make a call to sip:user at domain, blink appends
> ;transport parameter to request uri, for example:
>
> INVITE sip:3333 at sip2sip.info;transport=tcp SIP/2.0
>
> when my ob proxy receives such a request uri, it tries to contact
> sip2sip.info using tcp, which fails, because sip2sip server does not
> support tcp.
>
> blink should not add any ;transport parameter to request uri on its own,
> but just use the specified transport when it contacts its ob proxy.
>
> -- juha
> _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
>
More information about the Blink
mailing list