< Previous by Date | Date Index | Next by Date > |
Thread Index | Next in Thread > |
Hi All, As far as I know that SIP ACK is used only for final
response of INVITE msg, but LinkSys PAP2 used it for Register response. Are there any SIP RFCs to allow it? Here is the sip trace: [04/28/07 05:34:14.775975](sipServer00|3697826736)Rcv Stack
Msg: REGISTER sip:sip01.mynetfone.com.au SIP/2.0^M Via: SIP/2.0/UDP
124.189.51.79:5060;branch=z9hG4bK-8310ea79^M Max-Forwards: 70^M Contact: 09123994
<sip:09123994@xxxxxxxxxxxxx:5060>;expires=240^M To: 09123994 <sip:09123994@xxxxxxxxxxxxxxxxxxxxxx>^M From: 09123994
<sip:09123994@xxxxxxxxxxxxxxxxxxxxxx>;tag=2d656c4829c17b7ao0^M Call-ID: b3bb7dca-a99dbfba@xxxxxxxxxxxxx^M CSeq: 62263 REGISTER^M Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS,
REFER^M Supported: x-sipura^M User-Agent: Linksys/PAP2-3.1.9(LSc)^M Content-Length: 0^M [04/28/07 05:34:14.776328](sipServer00|4050291632)CallObj
266 Id b3bb7dca-a99dbf ba@xxxxxxxxxxxxx snd SIP STATUS 401 Msg SIP/2.0 401 Unauthorized^M Via: SIP/2.0/UDP
124.189.51.79:5060;branch=z9hG4bK-8310ea79^M To:
"09123994"<sip:09123994@xxxxxxxxxxxxxxxxxxxxxx>^M From:
<sip:09123994@xxxxxxxxxxxxxxxxxxxxxx>;tag=2d656c4829c17b7ao0^M Call-ID: b3bb7dca-a99dbfba@xxxxxxxxxxxxx^M CSeq: 62263 REGISTER^M User-Agent: EN2.5.23^M WWW-Authenticate: Digest
nonce="626791f8_00266",realm="my.com",algorithm=MD5^M Content-Length: 0^M [04/28/07 05:32:14.799145](sipServer00|3697826736)Rcv Stack
Msg: ACK sip:09123994@xxxxxxxxxxxxxxxxxxxxxx SIP/2.0^M Via: SIP/2.0/UDP
124.189.51.79:5060;branch=z9hG4bK-49c0bda0^M To: "09123994"
<sip:09123994@xxxxxxxxxxxxxxxxxxxxxx>^M From:
<sip:09123994@xxxxxxxxxxxxxxxxxxxxxx>;tag=2d656c4829c17b7ao0^M Call-ID: b3bb7dca-a99dbfba@xxxxxxxxxxxxx^M CSeq: 62261 ACK^M Content-Length: 0^M ^M Regards, Frank Y |