Superservlet completion 40%

Doinvite () done/missing status procession

Dosucesseresponse () done/missing status procession

Addsdpmrs () done

Dorequest () done/missing status procession

Doprovisionalresponse () done/missing status procession

 

 

Whether it is a call persistence or waiting signal, the server does not actually care about it. You only need to confirm that it contains sendonly, and add Mrs without sendonly. recvonly is the same.

 

The key is how to handle the 200 OK message sent by B to the server after C is maintained. The server removes the SDP message and sends it to a. A returns ack and sends it to B through the server, at this time, the server will first initiate re-invite to a. After receiving 200 (sdp a), the server will send re-invite (sdp a) to B. How can this logic be implemented...

 

It should be feasible to use the state machine. The key is that it is unclear what conditions are used to activate and send reinvite to both sides.

 

Problems solved in the last few days:

1. Functions of SIP. xml and compilation

2. The respective scopes of SIP. xml and IFC

3. If you want to process the proxy servlet, set USERPROFILE

4. No AR (Application router), yes, no ar!