|Subject:||Re: [osip-dev] Generic question about osip INVITE transaction|
|Date:||Mon, 22 Dec 2014 14:54:25 +0530|
All good so!
Happy Christmas and happy new year to all!
AymericLe 22 déc. 2014 03:33, "Austin Einter" <address@hidden> a écrit :_______________________________________________AustinThanksIn my transport callback, somehow it was not returning 0, hence because of transport error, transaction was getting TERMINATED.Hi AllI have resolved it. It was my mistake.On Sun, Dec 21, 2014 at 6:52 PM, Austin Einter <address@hidden> wrote:AustinBest RegardsCan this cause transaction to terminate.So the time difference is around 5 sec.2. When B tried to send 180, that time timestamp was 18:49:02:6081191. The first INVITE from A was at 18:48:57:395831From timestamp perspective, wireshark showsCan somebody kindly suggest whey the transaction state is TERMINATED and how this situation can be handled.5. Party A gets PRACK response and sends UPDATE to B.2. On getting INVITE at Party B, it sends 183 and create a dailog as uas.1. Party A sent INVITE to Party B.Now I am stuck with below scenario.So far I am comfortable and able to send / receive couple of messages.Hi AllI have been trying to do experiment with OSIP for multiple cases.
3. Party A on getting 183, creates dailog as uac and sent PRACK
4.Party B gets PRACK and sends PRACK response 200 K.6. B gets UPDATE, and then sends 200 OK for UPDATE.7. Now B tries to send 180, but finds original INVITE transaction state is TERMINATED.
osip-dev mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|