[reSIProcate] how resip process CANCEL after send 200 OK before get ACK?
- From: "maodonghu" <hhmmdd@xxxxxxx>
- Date: Tue, 19 Sep 2006 14:58:18 +0800
resip
INFO | 20060919-143056.812 | NV3_SIP_TEL | RESIP:DUM | 2680 |
DialogUsageManager.cxx:1168 | Got: SipReq: INVITE 239@xxxxxxxxx:37060
tid=a262606232d54.1 cseq=INVITE contact=210@xxxxxxxxxxxxxx:5060 / 1 from(wire)
INFO | 20060919-143056.812 | NV3_SIP_TEL | RESIP:DUM | 2680 |
InviteSession.cxx:2045 | Transition UAS_Start -> UAS_Offer
INFO | 20060919-143056.812 | NV3_SIP_TEL | RESIP:DUM | 2680 |
ServerInviteSession.cxx:91 | UAS_Offer: provisional(180)
INFO | 20060919-143056.812 | NV3_SIP_TEL | RESIP:DUM | 2680 |
InviteSession.cxx:2045 | Transition UAS_Offer -> UAS_EarlyOffer
INFO | 20060919-143056.812 | NV3_SIP_TEL | RESIP:DUM | 2680 |
ServerInviteSession.cxx:251 | UAS_EarlyOffer: provideAnswer
INFO | 20060919-143056.812 | NV3_SIP_TEL | RESIP:DUM | 2680 |
InviteSession.cxx:2045 | Transition UAS_EarlyOffer -> UAS_EarlyProvidedAnswer
INFO | 20060919-143056.890 | NV3_SIP_TEL | RESIP:DUM | 2680 |
ServerInviteSession.cxx:443 | UAS_EarlyProvidedAnswer: accept(200)
INFO | 20060919-143056.890 | NV3_SIP_TEL | RESIP:DUM | 2680 |
InviteSession.cxx:2045 | Transition UAS_EarlyProvidedAnswer -> UAS_Accepted
INFO | 20060919-143056.906 | NV3_SIP_TEL | RESIP:DUM | 2680 |
DialogUsageManager.cxx:1168 | Got: SipReq: CANCEL 239@xxxxxxxxx:37060
tid=a262606232d54.1 cseq=CANCEL / 1 from(wire)
INFO | 20060919-143056.906 | NV3_SIP_TEL | RESIP:DUM | 2680 |
ServerInviteSession.cxx:684 | dispatchAccepted: SipReq: CANCEL
239@xxxxxxxxx:37060 tid=a262606232d54.1 cseq=CANCEL / 1 from(wire)
INFO | 20060919-143057.390 | NV3_SIP_TEL | RESIP:DUM | 2680 |
InviteSession.cxx:776 | Retransmitting:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.101.59:5060;branch=z9hG4bKa262606232d54.1
Via: SIP/2.0/UDP
192.168.101.5:28410;branch=z9hG4bK-d87543-121455157566a77c-1--d87543-;rport=28410
Record-Route: <sip:192.168.101.59:5060;lr>
Contact: <sip:239@xxxxxxxxx:37060>
To: "239"<sip:239@xxxxxxxxxxxxxx:5060>;tag=161ace4b
From: "210"<sip:210@xxxxxxxxxxxxxx>;tag=fa0cc836
Call-ID: ae57920412396477YWYxMWZiODE3NzFmMDQxMGFmMTNlOTU3NjBlNGI2Njg.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY
Content-Type: application/sdp
User-Agent: eWings-NetVoice/3.0
Content-Length: 177
v=0
o=0 239 239 IN IP4 192.168.101.59
s=NetVoice3
c=IN IP4 192.168.101.59
t=0 0
m=audio 5660 RTP/AVP 0 101
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
INFO | 20060919-143058.390 | NV3_SIP_TEL | RESIP:DUM | 2680 |
InviteSession.cxx:776 | Retransmitting:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.101.59:5060;branch=z9hG4bKa262606232d54.1
Via: SIP/2.0/UDP
192.168.101.5:28410;branch=z9hG4bK-d87543-121455157566a77c-1--d87543-;rport=28410
Record-Route: <sip:192.168.101.59:5060;lr>
Contact: <sip:239@xxxxxxxxx:37060>
To: "239"<sip:239@xxxxxxxxxxxxxx:5060>;tag=161ace4b
From: "210"<sip:210@xxxxxxxxxxxxxx>;tag=fa0cc836
Call-ID: ae57920412396477YWYxMWZiODE3NzFmMDQxMGFmMTNlOTU3NjBlNGI2Njg.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY
Content-Type: application/sdp
User-Agent: eWings-NetVoice/3.0
Content-Length: 177
v=0
o=0 239 239 IN IP4 192.168.101.59
s=NetVoice3
c=IN IP4 192.168.101.59
t=0 0
m=audio 5660 RTP/AVP 0 101
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
INFO | 20060919-143100.390 | NV3_SIP_TEL | RESIP:DUM | 2680 |
InviteSession.cxx:776 | Retransmitting:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.101.59:5060;branch=z9hG4bKa262606232d54.1
Via: SIP/2.0/UDP
192.168.101.5:28410;branch=z9hG4bK-d87543-121455157566a77c-1--d87543-;rport=28410
Record-Route: <sip:192.168.101.59:5060;lr>
Contact: <sip:239@xxxxxxxxx:37060>
To: "239"<sip:239@xxxxxxxxxxxxxx:5060>;tag=161ace4b
From: "210"<sip:210@xxxxxxxxxxxxxx>;tag=fa0cc836
Call-ID: ae57920412396477YWYxMWZiODE3NzFmMDQxMGFmMTNlOTU3NjBlNGI2Njg.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY
Content-Type: application/sdp
User-Agent: eWings-NetVoice/3.0
Content-Length: 177
v=0
o=0 239 239 IN IP4 192.168.101.59
s=NetVoice3
c=IN IP4 192.168.101.59
t=0 0
m=audio 5660 RTP/AVP 0 101
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
INFO | 20060919-143104.390 | NV3_SIP_TEL | RESIP:DUM | 2680 |
InviteSession.cxx:776 | Retransmitting:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.101.59:5060;branch=z9hG4bKa262606232d54.1
Via: SIP/2.0/UDP
192.168.101.5:28410;branch=z9hG4bK-d87543-121455157566a77c-1--d87543-;rport=28410
Record-Route: <sip:192.168.101.59:5060;lr>
Contact: <sip:239@xxxxxxxxx:37060>
To: "239"<sip:239@xxxxxxxxxxxxxx:5060>;tag=161ace4b
From: "210"<sip:210@xxxxxxxxxxxxxx>;tag=fa0cc836
Call-ID: ae57920412396477YWYxMWZiODE3NzFmMDQxMGFmMTNlOTU3NjBlNGI2Njg.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY
Content-Type: application/sdp
User-Agent: eWings-NetVoice/3.0
Content-Length: 177
v=0
o=0 239 239 IN IP4 192.168.101.59
s=NetVoice3
c=IN IP4 192.168.101.59
t=0 0
m=audio 5660 RTP/AVP 0 101
a=fmtp:101 0-15
a=rtpmap:101 telephone-event/8000
a=sendrecv
maodonghu
hhmmdd@xxxxxxx
2006-09-19