On Mon, Jan 4, 2010 at 11:38 AM, Damien Sandras <[email protected]> wrote: > > Second, we have a bug in some registrars. This is where we put in a contact > field of something like: > > > > Contact: <sip:[email protected]:5060> > > > > And they reply with a contact field of: > > > > Contact: <sip:[email protected]> > > > > And that is NOT THE SAME THING, as per the RFC3261 rules. Section 10.3 says > the registrar MUST reply with the contact, and technically it doesn’t. > > > > > > So, I cannot remove the line as described. > > > > And I am not sure how to work around this bug in the registrar either. Last > time it happened (on a paid consulting job) we got the registrar people to > fix the issue. I don’t know if this is an option in this case.
I've seen this the other way around. The Cisco CallManager we have here replies with Contact: <sip:[email protected]:5060> to REGISTER w/ Contact: <sip:[email protected]>, same for Linksys SPA9000. We worked around it in our app by always including port in the Contact URI. -- Ian _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
