[removed resiprocate-devel]
The 2nd REGISTER request should be a new SIP transaction
– did you reset the branch parameter on the via header before sending it out?
Scott
From: resiprocate-users-bounces@xxxxxxxxxxxxxxx
[mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Sonika
Jindal
Sent: September-10-08 5:07 AM
To: resiprocate-users@xxxxxxxxxxxxxxx; resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate-users] Stack not sending response to application
Hi,
I am stuck in once case.
The scenario is as follows:
My
Client
IMS Server
=======
========
REGISTER ----------------------------------->
<--------------------------------- 401 (with challenge)
REGISTER ----------------------------------->
(with response for challenge)
<---------------------------------- 403
When the stack receives 403 response, it doesn't send it to the application.
I am using stack. I am not using dum.
Debugging into it, I found that when 401 is recieved, the state becomes
Completed and then when 403 comes the state is Completed, so the stack deletes
the message.
As of now, while sending the second REGISTER , I set the state to Trying. Then
I am able to get 403 at the application.
Is this the proper way ? What do I need to do to solve it?
Thanks,
Sonika