> In version 4.0.1-015537, when I register from a remote NATed > phone, I'm seeing OPTIONS requests from sipXecs (I assume > they are coming from sipXproxy). I have a question and a > comment about these: > > * They set all four addresses (request URI, To, From, > and Contact) > to 'sip:[email protected]' - why? > > This isn't a valid address for my UA - since the > proxy knows the > Contact I registered, wouldn't it be better to use > that for the > request uri and To headers and put a fixed reserved address in > the From and Contact headers? > > I know we don't care whether or not this request 'succeeds', > since the only point is really to elicit some response and the > 404 my phone is sending is as good as any other for > that, but it > seems it would be better not to have error responses > in logs if > we can avoid them without too much work.
The NAT maintainer has to craft an Options message every 20 seconds for every remote worker on the system so the number of messages it send can build up quite rapidly. For efficiency reasons, I decided to go with a 'constant' message to avoid taking the performance hit associated with Url->String/String->Url conversions. I can try and quantify that 'hit' but that is going to be pretty low in my list of priorities right now. > > * This request does not have a User-Agent header - for > diagnostic > purposes it would be much better if it identified > itself (_all_ > requests and responses generated by sipXecs services should > include either a User-Agent or Server header as appropriate). Very good suggestion. I just added a Server header. Will be part of my next commit. > > > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
