An ACK for REGISTER? Not only is it highly likely to be a hacking attempt, you got a bunch of clowns behind it.
On 01/27/2012 10:04 AM, Nathaniel Watkins wrote: > RANCH\nACKsip:[email protected] SIP/2.0\r\nVia: SIP/2.0/UDP > 188.138.116.36:5211;branch=z9hG4bK-179067399;rport=5211\r\nContent-Length: > 0\r\nFrom: \"1\"<sip:[email protected]>; > tag=310132343934303034393930\r\nAccept: application/sdp\r\nUser-Agent: > friendly-scanner\r\nTo: > \"1\"<sip:[email protected]>\r\nContact:<sip:[email protected];x-sipX-nonat>\r\nCseq: > 1 REGISTER ACK\r\nCall-Id: 2236359437\r\nMax-Forwards: 20\r\nDate: Thu, 26 > Jan 2012 09:18:36 GMT\r\n\r\n\n SipTransaction dump:\n this: > 0xb3f26580\n hash: 2236359437c1\n mCallId: 2236359437\n > mpBranchId->data(): z9hG4bK-XX-800aPJLheelC0X36LoCQ4RYI1g\n > mRequestUri:sip:[email protected]\n mSendToAddress: 208.33.156.137\n > mSendToPort: -1\n mSendToProtocol: UNKNOWN\n mCancelReasonValue: > \n mpDnsSrvRecords: NULL\n mFromField: \" > 1\"<sip:[email protected]>;tag=310132343934303034393930\n mToField: > \"1\"<sip:[email protected]>\n mRequestMethod: ACK\n mCseq: 1\n > mIsServerTransaction: FALSE\n _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
