Unspecified transport in ACK?

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

 



On Tue, Jun 23, 2009 at 4:31 PM, Giorgio Bongiorni <g.bongiorni at selta.it>wrote:

> Hi Benny and all,
> I wish to make a call towards an IP phone.
> In "remote_uri" and "target" params of "pjsip_dlg_create_uac" I specified
> the transport (UDP)
>
>   pj_str_t remote_uri = pj_str("<sip:201 at 10.13.0.104:5060
> ;transport=UDP>");
>
> and after creating invite session I set the transport for the dialog within
> INVITE session
>
>   pjsip_tpselector tp_sel;       tp_sel.type = PJSIP_TPSELECTOR_TRANSPORT;
>   tp_sel.u.transport = g_transport;
>   pjsip_dlg_set_transport(g_inv->dlg, &tp_sel);
>
> Everything seems to work well, but when ACK is sent I get this message
>
>   Target '10.13.0.104:5060' type=Unspecified resolved to '10.13.0.104:5060'
> type=UDP (UDP transport)
>
> Am I missing anything? Any help is appreciated.
>

I don't think there's anything to worry about there. The "type=Unspecified"
just means that remote doesn't put transport parameter in its Contact URI,
and we're just following RFC 3261/3263 to resolve it.

Cheers
 Benny



> Thank you,
>
> Giorgio Bongiorni
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090711/dbc34bd3/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