Here is one with multiple Accept lines (like RFC4662 examples) which is rejected:
SUBSCRIBE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 192.168.10.12:5060;branch=z9hG4bK8cd1664f33814ecb;rport From: 911 <sip:[email protected]>;tag=8cd1664f33350388 To: "Resource List" <sip:[email protected]> Call-ID: [email protected] CSeq: 2 SUBSCRIBE Max-Forwards: 70 Expires: 3600 Event: dialog Accept: application/dialog-info+xml Accept: application/rlmi+xml Accept: multipart/related Supported: eventlist,timer Contact: <sip:[email protected]> Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY, MESSAGE User-Agent: VOP/1.4.3 Authorization: Digest realm="ip15.joher.com",nonce="d725bf83241972ef41f9cd8181e201914c7ba0e4",response="a257bdfa7fdc5fadc3fee578d7e44f65",username="911",uri="sip:[email protected]",qop="auth",cnonce="038e9409",nc="00000002" Content-Length: 0 SIP/2.0 415 Unsupported Media Type or Content Encoding Record-Route: <sip:192.168.10.15:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%7EOGNkMTY2NGYzMzM1MDM4OA%60%60%216dabbfefd6ea4ca7e5672113f32f0542;x-sipX-done> From: 911 <sip:[email protected]>;tag=8cd1664f33350388 To: "Resource List" <sip:[email protected]>;tag=BNHkfV Call-Id: [email protected] Cseq: 2 SUBSCRIBE Via: SIP/2.0/UDP 192.168.10.12:5060;branch=z9hG4bK8cd1664f33814ecb;rport=5060 Expires: 2464 Accept: multipart/related;type="application/rlmi+xml";start="<[email protected]>";boundary="f77f0689" Contact: sip:[email protected]:5140 Date: Mon, 30 Aug 2010 12:15:32 GMT Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, SUBSCRIBE, MESSAGE User-Agent: sipXecs/4.2.1 sipXecs/rls (Linux) Accept-Language: en Require: eventlist Content-Length: 0 And here is another one with a single Accept line which is accepted: SUBSCRIBE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 192.168.10.12:5060;branch=z9hG4bK8cd16652571fee6c;rport From: 911 <sip:[email protected]>;tag=8cd1665256d3a328 To: "Resource List" <sip:[email protected]> Call-ID: [email protected] CSeq: 2 SUBSCRIBE Max-Forwards: 70 Expires: 3600 Event: dialog Accept: application/dialog-info+xml,application/rlmi+xml,multipart/related Supported: eventlist,timer Contact: <sip:[email protected]> Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, NOTIFY, MESSAGE User-Agent: VOP/1.4.3 Authorization: Digest realm="ip15.joher.com",nonce="e12c6a2cca74dd5e5709673b695b155d4c7ba138",response="6e8e1e3cc42e0bd98b356207d27900d1",username="911",uri="sip:[email protected]",qop="auth",cnonce="4b1b96f5",nc="00000003" Content-Length: 0 SIP/2.0 202 Accepted Record-Route: <sip:192.168.10.15:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%7EOGNkMTY2NTI1NmQzYTMyOA%60%60%2114cb88e79ee49d687f5e7d370e0280fe;x-sipX-done> From: 911 <sip:[email protected]>;tag=8cd1665256d3a328 To: "Resource List" <sip:[email protected]>;tag=FuP2k3 Call-Id: [email protected] Cseq: 2 SUBSCRIBE Via: SIP/2.0/UDP 192.168.10.12:5060;branch=z9hG4bK8cd16652571fee6c;rport=5060 Expires: 3128 Contact: sip:[email protected]:5140 Date: Mon, 30 Aug 2010 12:16:56 GMT Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, SUBSCRIBE, MESSAGE User-Agent: sipXecs/4.2.1 sipXecs/rls (Linux) Accept-Language: en Require: eventlist Content-Length: 0 Worley, Dale R (Dale) wrote: > Can you give me a specific SUBSCRIBE message that fails but should > not? That will make it far easier to diagnose the problem. > Thank you for paying attention to what I write, > > Dale > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
