[reSIProcate] Call teardown question

Kovar, William (Bill) bkovar at avaya.com
Wed Feb 28 12:28:28 CST 2007


I'm seeing some behavior in DUM that may or may not be correct.

The scenario is as follows:

					 DUM
UA1----------------------------B2B-----------------------------UA2
					 |
	<------- INVITE (No SDP) |
	180 -------------------->|
	200 (SDP)  ------------->|--------- INVITE (SDP) --------->
					 |<----------------------------
180
		......32 seconds...|
	BYE -------------------->|

In the scenario above, the BYE falls into the following code:

 ![2007-02-28 17:05:08.968] <2020:RESIP:DUM>  WARNING |
ClientInviteSession.cxx:852 | Don't know what this is : BYE
sip:56000 at 135.8.116.33:5060 SIP/2.0

There is nothing done in ClientInviteSession::dispatchStart(). 

Is there an expectation that UA1 is supposed to send something like a
487?? My research shows that this BYE is legal in this scenario, which
leave me with an incomplete transaction. 

If the BYE is not sent to onTerminated() how do I know to tear down the
call?


Bill Kovar
 




More information about the resiprocate-devel mailing list