<DIV>Jiri,</DIV>
<DIV> </DIV>
<DIV>You are correct. Everything is working except for the error messages, which concern me since I don't know why they're occuring or if they might cause instability.</DIV>
<DIV> </DIV>
<DIV>I'll try the CVS version.<BR><BR>Thanks,</DIV>
<DIV>G.</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"><sip:650218888<br><mailto:4@10.10.10.5><BR>So I don't understand from your description -- is there anything what is not working except<BR>some error messages?<BR><BR>>What I really need now is a way to deal with the timer issue. Jiri, I don't think I need multiple timers. I never want SER to timeout calls placed to the PSTN. I just want one timer which I can apply to selective transactions. <BR><BR>Well, there is _always_ a timer for every transaction and the timer has always<BR>the same value. The only thing which can be made distinctive is how this timer<BR>is handled.<BR><BR>>Right now, the timer causes all calls to fail. I understand that I can change processing on failure, and I am doing this, but it would be very nice if the timer could be used only for specific transactions. I think this would involve setting it through a function call instead of a modparam call, but I
don't know since I haven't actually looked at any code.<BR><BR>The timer can't be removed -- it has a kind of "garbage collection" responsibility<BR>and a server without timers would run out of memory very quickly.<BR><BR>What you could do is forwarding to gateway statelessly -- then, there would be<BR>indeed no timer involved. I don't think, that makes sense though for a couple<BR>of other reasons like accounting and/or tcp2udp forwarding.<BR><BR>>I've also tried to just relay PSTN calls again (re-relay) through a failure route after the timer expires, but that doesn't seem to be working too well. Is this possible?<BR><BR>What does it mean "it doesn't seem to be working too well"?<BR><BR>Anyway, I think it really would not work -- it would end up<BR>canceling and re-ringing the PSTN destination, which is a kind<BR>of undesirable behviour.<BR><BR>So in summary, I don't think there is an easy option for single-instance<BR>ser and multiple-timer. A really straight-forward option is
support in<BR>SER.<BR><BR>>Also, I think its not necessary to implement the "single-ser" config that is capable of running voicemail if this dual configuration works well. Of cource, the "single-ser" config would make it a little simpler for users.<BR><BR>I would actually love to have it, it is just a problem of my time.<BR><BR>-jiri <BR></BLOCKQUOTE></mailto:4@10.10.10.5></sip:650218888<br><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext%2Csec%3Amail">The New Yahoo! Shopping</a> - with improved product search