Thanks, Jiri. Jiri Kuthan <jiri(a)iptel.org> wrote: [...] Ah, but that breaks failover to voicemail, no? (within a reasonable time) Yeah, the failure_route for voicemail would be turning that off. I'm still confused, though. I need to be able to forward calls to the PSTN and let them ring indefinitely, leaving any call resolution to the remote end (say, the PSTN user's PBX, voicemail, whatever). forward() works great for that, but if my caller is going through NAT I have to use t_relay. A high fr_inv_timer means incoming calls can't fall back to voicemail in a reasonable time, though it does fix the problem for outgoing PSTN calls. So I guess one option would be to run 2 instances of ser, one for incoming and another for outgoing. Seems like a lot of administrative overhead just to fix this one minor problem. But if that's what I gotta do, that's what I'll do. I believe I saw someone mention a solution like this in an archived list thread. Has anyone done any work on making the module parameters settable from within the route blocks? That would make this a whole lot easier -- I could just turn the timer off in the NAT -> PSTN instance and everything would be good. Thanks again for your help, and best regards. -- = o'shaughnessy evans = = sys admin @ (aloha|kona|myworld).net = "We've got a lot of suppliers. We already know some of them are pretty good and some of them are idiots. We don't expect the Y2K problem to change this." -- http://www.hartscientific.com/y2k.htm

Jiri Kuthan <jiri(a)iptel.org> wrote: [...] Oops. I mistated -- there's no failure_route defined when routing to the PSTN. The fr_inv_timer is still triggering a failure, though. I wish calls to remote endpoints over which I have no control (in this case, PSTN destinations) to ring as long as the remote system determines. Only local calls should fall back to voicemail. Here's the nitty gritty of the problem. I have fr_inv_timer set to some normal value, like 30-45 seconds, so that if a local user doesn't pick up his phone within, say, 6 rings or so, the call will fail over to his voicemail box. t_on_failure is only set in this route. That works great. In a different route, I send calls to the PSTN. If the caller isn't coming from a NAT device, I can use forward(). No need to do a stateful relay because I'm not doing any accounting. I just want to hand off the call and forget about it. But if the caller *is* coming via NAT, I need to force_rtp_proxy, which thus means t_relay instead, right? And since I'm using the tm module, the fr_inv_timer triggers after 45 seconds and I get a busy signal (since there's no failure_route defined). Is there a way to avoid that bogus fr_inv_timer failure? I don't know enough about call routing to say, but from this perspective it seems to me that if there's no failure_route defined, the fr_inv_timer should never go off. Anyway, thanks again for your help, everyone. -- = o'shaughnessy evans = = sys admin @ (aloha|kona|myworld).net = "There is an old saying that if a million monkeys typed on a million keyboards for a million years, eventually all the works of Shakespeare would be produced. Now, thanks to Usenet, we know this is not true."

O'Shaughnessy Evans wrote: We have several instances of SER running for just this purpose. One instance with a specific value for fr_inv_timer for inbound calls that need to goto SEMS after 4 rings. A different instance for outbound calls where fr_inv_timer is set to 45 seconds to handle the range of called devices and their resective "answer" times. This works pretty well.