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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org