[Freeswitch-users] Behaviour for SIP Contact header without ; transport=

[Mikael Bjerkeland]

Yeah, that's what's happening, but is it the expected behaviour? It seems to
me that either FS or Nokia's doing something wrong here, otherwise Transport
Type: Auto is useless unless UDP is the lowest weight in the NAPTR record,
since incoming calls will fail when registered with TCP if != transport=TCP.



2009/4/24 Michael Jerris <mike at jerris.com>

> If you don't include the transport= in the message, the reply to that
> register should still go back on tcp, but the calls to that registered
> endpoint will go on upd.
>
> Mike
>
> On Apr 24, 2009, at 6:19 AM, Mikael Aleksander Bjerkeland wrote:
>
> > Hi,
> >
> > I'm registering a Nokia N82 with FreeSWITCH, where the hostname has
> > NAPTR and SRV records pointing to the server in the following order:
> > TLS, TCP and UDP.
> >
> > If I set my Nokia phone to use transport type: Auto it registers to FS
> > with TCP, but it doesn't have transport=TCP in the Contact header. FS
> > receives SIP messages from the phone in TCP but replies in UDP due to
> > the Contact missing transport=TCP. The phone doesn't acknowledge any
> > UDP
> > traffic since it initially registered with TCP.
> >
> > If I change transport type to either TCP or UDP things start to work
> > as
> > the phone adds the appropriate ;transport= tag.
> > Is this the expected behaviour? Is FS or the phone doing something
> > wrong
> > here? Should a UAS assume transport=TCP if the initial traffic
> > (REGISTER) is TCP and the transport= tag is missing?
> >
>
>
> _______________________________________________
> Freeswitch-users mailing list
> Freeswitch-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20090424/d2344c3a/attachment-0002.html