Hi,
I am looking for a working ser.cfg which forwards all unanswered calls to voicemail after 10 seconds..
How is the correct usage of "modparam("tm", "fr_inv_timer", 8 )" ??
I tried to integrate the sample voicemail configuration from iptel's ser admin guide, but now ALL my calls are forwarded to voicemail...
I have read that it can be useful to run 2 instances of ser to integrate voicemail. Is this necessary ???
Oliver
Oliver Zilken wrote:
Hi,
I am looking for a working ser.cfg which forwards all unanswered calls to voicemail after 10 seconds..
How is the correct usage of "modparam("tm", "fr_inv_timer", 8 )" ??
I tried to integrate the sample voicemail configuration from iptel's ser admin guide, but now ALL my calls are forwarded to voicemail...
I have read that it can be useful to run 2 instances of ser to integrate voicemail. Is this necessary ???
From the documentation: "fr_inv_timer (integer) Timer which hits if no final reply for an INVITE arrives after a provisional message was received (in seconds)/ //Default value is 120 seconds."
/Running 2 instances of ser isn't necessary, but I have it working like that, because I don't want to run a CVS version of SER for call routing, but I want to run a CVS SER & SEMS for voicemail because the CVS version has more functionality and the SEMS CVS version is not compatibel with the stable SER version (0.8.12).
So you have two instances of ser. 1 main proxy and 1 voicemail. Those two examples are in CVS: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/examples/vm_proxy.c... http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/examples/voicemail....
Kind regards,
Geert
Hello Geert,
i just wanted to correct a small thing:
/Running 2 instances of ser isn't necessary, but I have it working like that, because I don't want to run a CVS version of SER for call routing, but I want to run a CVS SER & SEMS for voicemail because the CVS version has more functionality and the SEMS CVS version is not compatibel with the stable SER version (0.8.12).
The last CVS version of Sems IS compatible with Ser 0.8.12. In a way to avoid breaking compatibility with future developement, i just created a new branch: ser_rel_0_8_12. This branch will stay compatible with Ser 0.8.12. So, you don't need to run unstable version of Ser if you don't want to.
-Raphael.