Re: [reSIProcate] OnReferAccepted() called when SipFrag contain 408

["Kovar, William \(Bill\)" <bkovar@xxxxxxxxx>]

Scott,

 

Thanks for the clarification, but then I would ask why is OnReferAccepted called when a NOTIFY (code >=100) is sent and not on the actual 202??

 

Also, given your explanation below, when would OnReferRejected() be called? When a failure to accept the REFER is sent?

 

Bill Kovar

bkovar@xxxxxxxxx

Avaya, Inc.

(732) 852-2609

 

---

From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Monday, January 22, 2007 4:38 PM
To: Kovar, William (Bill); resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] OnReferAccepted() called when SipFrag contain 408

The Refer request was accepted, otherwise the other endpoint wouldn’t have sent a Notify.  The other endpoint is notifying you that could not reach the Refer destination – your application must always parse out the SipFrag Body and handle the embedded responses appropriately.

 

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Kovar, William (Bill)
Sent: Monday, January 22, 2007 4:07 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] OnReferAccepted() called when SipFrag contain 408

 

All,

 

Seeing some weird behavior in Dialog.cxx. Why would a onReferAccepted() be called when a 408 SipFrag is returned?? Shouldn't this cause OnReferRejected()??

 

See the trace below:

 

 

 

NOTIFY sip:55506@xxxxxxxxxxxx:5060 SIP/2.0

 

Via: SIP/2.0/UDP 135.8.52.181:5060;branch=z9hG4bK030303132626431616b2cc.0

 

Via: SIP/2.0/TCP 135.8.83.172;psrrposn=1;received=135.8.83.172;branch=z9hG4bK014e08ff8aadb1903f45bcb3e300

 

Max-Forwards: 69

 

Record-Route: <sip:135.8.52.181:5060;lr>

 

Contact: "SIP DEV's IP ph"<sip:70800@xxxxxxxxxxxx;transport=tcp>

 

To: "55506"<sip:55506@xxxxxxxxx>;tag=856f4606

 

From: "SIP DEV's IP ph"<sip:70800@xxxxxxxxx>;tag=0ba7d8df8aadb1833f45bcb3e300

 

Call-ID: 0ba7d8df8aadb1843f45bcb3e300

 

CSeq: 2 NOTIFY

 

Content-Type: message/sipfrag

 

User-Agent: Avaya CM/R013x.01.2.632.1

 

Subscription-State: terminated;reason=noresource

 

Event: refer

 

Content-Length: 29

 

 

 

SIP/2.0 408 Request Timeout

 

 ![2007-01-22 20:37:13.473] <5224:RESIP:DUM>  DEBUG | ClientSubscription.cxx:31 | ClientSubscription::ClientSubscription from SipReq:  NOTIFY 55506@xxxxxxxxxxxx:5060 tid=030303132626431616b2cc.0 cseq=NOTIFY contact=70800@xxxxxxxxxxxx / 2 from(wire)
 ![2007-01-22 20:37:13.473] <5224:RESIP:DUM>  DEBUG | Dialog.cxx:847 | +++++++ mRemoteTarget.Uri = sip:70800@xxxxxxxxxxxx;transport=tcp
 ![2007-01-22 20:37:13.473] <5224:RESIP:DUM>  DEBUG | Dialog.cxx:849 | +++++++ Rline = SUBSCRIBE sip:70800@xxxxxxxxxxxx;transport=tcp SIP/2.0
 ![2007-01-22 20:37:13.473] <5224:RESIP:DUM>  DEBUG | Dialog.cxx:914 | Dialog::makeRequest: SUBSCRIBE sip:70800@xxxxxxxxxxxx;transport=tcp SIP/2.0

 

Via: SIP/2.0/ ;branch=z9hG4bK-d87543-367f846ff920d910-1--d87543-;rport

 

Max-Forwards: 70

 

Route: <sip:135.8.52.181:5060;lr>

 

Route: <sip:135.8.83.172;lr;transport=tcp>

 

Contact: <sip:55506@xxxxxxxxxxxx:5060>

 

To: "SIP DEV's IP ph"<sip:70800@xxxxxxxxx>;tag=0ba7d8df8aadb1833f45bcb3e300

 

From: "55506"<sip:55506@xxxxxxxxx>;tag=856f4606

 

Call-ID: 0ba7d8df8aadb1843f45bcb3e300

 

CSeq: 4 SUBSCRIBE

 

Event: refer

 

Content-Length: 0

 

 

 

 ![2007-01-22 20:37:13.473] <5224:RESIP:APP>  INFO | UserAgent.cpp:1897 | sip:55506@xxxxxxxxx CUserAgent::onReferAccepted(ISH) on session 5 - SipReq:  NOTIFY 55506@xxxxxxxxxxxx:5060 tid=030303132626431616b2cc.0 cseq=NOTIFY contact=70800@xxxxxxxxxxxx / 2 from(wire)
 

 

Bill Kovar

bkovar@xxxxxxxxx

Avaya, Inc.

(732) 852-2609