-----Original Message----- From: Joegen Baclor [mailto:[email protected]] Sent: Sunday, 4 September 2011 11:32 AM To: Iñaki Baz Castillo Cc: Aaron Clauson; [email protected] Subject: Re: [Sip-implementors] Registration "Policing"
On 09/04/2011 02:30 AM, Iñaki Baz Castillo wrote: > 2011/9/3 Aaron Clauson<[email protected]>: >>> I've had a user come to me with a problem where they can't get calls through >>> to one of their suppliers because the Contact URI on the INVITE request >>> doesn't match the Contact URI on their registration binding. >> Such "annoying" policy means that the proxy/registrar just wants to >> talk with stupid phones, those which are supposed to use a single >> socket for all, a single "line", a single AoR, and so. It's indeed >> sad. I've never seen something so "strict". > I have seen such behavior from a popular switch and needed to modify my > SBC code to lookup the binding from the registrar and rewrite the > contact URI. Sadly, this is something that a proxy can't do and one of > those various reasons why people resort to SBC's. Hi Joegen, so did you include logic in your SBC to ensure INVITE requests contain the same URI in the Contact header as a registrar binding? If so what was the main goal? Was it to heighten security? If I was an attacker it would be trivial for me to send a REGISTER request immediately prior to an INVITE request if I had compromised credentials. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
