Re: Help with changing SIP Stack Request retransmit setting

Could you just send the OPTIONS/NOTIFY request statelessly, then have
your application implement whatever logic you need for timeouts,
retransmissions, etc?

--Ryan

P.S.  I know this is a stale thread but I was browsing the archives and
this caught my eye -- I programmed a similar change to the stack for an
application that sends OPTIONS requests to qualify registered contacts
... email me if anyone wants details or patch.


Amos K wrote:
> Hi Guys,
>
> I am working on a SIP NOTIFY/OPTION application and I am using the
> JAIN NIST reference implementation of the SipStack.
>  
> *Problem*:
> When a NOTIFY/OPTION request is sent to ...for example a SIP phone
> with a bad or non existing IP Address via the sipstack, the stack
> retransmits the NOTIFY request at the intervals of 500 ms, 1 s, 2 s, 4
> s, 4 s, 4 s, etc until the request finally times out. In all, there
> could be up to 8 NOTIFY or more requests before the request times out.
>  
> *Desired:*
> I want to be able to configure the sipstack to limit the number of
> retransmission of NOTIFY/OPTION requests that can be sent before the
> request times out. For my application, 4 or less retransmit
> NOTIFY/OPTION requests is ok. Or I want the intial request to Timeout
> after say 4s instead of 32s.
>  
> *I've tried:*
> Using the RetransmitTimer but it throws exceptions....
> ClientTransaction /trans/ *= *
> /udpProvider/*.getNewClientTransaction(*/ request/*);*
> /trans/*.setRetransmitTimer (10*00*);*
> /trans/*.sendRequest ();*
> ** 
> *Solution:*
> ?
>  
> Thanks
>  
> Sincerely,
> Amos.
> ------------------------------------------------------------------------
>
> _______________________________________________
> nist-sip mailing list
> [email protected]
> http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>   


-- 
Ryan Mitchell <[email protected]>
Telecom Logic, LLC
503-943-2980