[reSIProcate] Help on SUBSCRIBE behaviour in TCP

[parimala.gopalakrishna at wipro.com]

Hi,
 
I am using SUBSCRIBE-NOTIFY mechanism in my module. 
I am using Resiprocate Stack.
 
I am writing an application as a Subscriber and initiating a
Subscription.
I have derived from ClientSubscriptionHandler and defined the callbacks.
 
Scenario:
When I am running Subscriber in TCP mode an when Notifier is not
running:
 
Subscriber tries to open a socket for TCP connection and fails as
Notifier is not running.
But here 503 Service Unavailable response is received and an exception
is caught telling:  "Subscription-State"  Header is missing in the
Response.
I have attached the log file:TCP_log.txt, please have a look at it.
 
Subscription State Header is not mandatory in the Error Responses.
The match is done based on CallId, From tag and CSeq No.  according to
RFC3265 
Why is it throwing the Exception?
--------------
 
My purpose is: The Subscriber should keep on trying to send SUBSCRIBE
till the Notifier comes up or starts listening.
 
Should I run a new timer in my application or can I reuse from the
stack.
 
Can someone explain the purpose of onRequestRetry() callback?
How should I proceed?
 
Please reply.
 
Regards,
Parimala
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060614/a8d7cd69/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: TCP_log.txt
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060614/a8d7cd69/attachment.txt>