Hello friends,
Is it possible for SER to forward a call to another phone if the recipient does not answer?
Thanks, Dan
Daniel Sullivan writes:
Is it possible for SER to forward a call to another phone if the recipient does not answer?
this could be achieved with sequential forking (by trying contacts in decreasing q order), but sequential forking is not yet supported in ser.
-- juha
Is it possible to forward to another user if the current user is busy? Like a hunt group?
---greg
-----Original Message----- From: serusers-admin@lists.iptel.org [mailto:serusers-admin@lists.iptel.org] On Behalf Of Juha Heinanen Sent: Tuesday, March 18, 2003 9:56 AM To: Daniel Sullivan Cc: serusers@lists.iptel.org Subject: [Serusers] call forward on no answer
Daniel Sullivan writes:
Is it possible for SER to forward a call to another phone
if the recipient
does not answer?
this could be achieved with sequential forking (by trying contacts in decreasing q order), but sequential forking is not yet supported in ser.
-- juha _______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Greg Fausak writes:
Is it possible to forward to another user if the current user is busy? Like a hunt group?
you can do these kind of functions in many different places of the system. the proxy works on contact information based on q values, your sip phone can have such a forwarding feature, and finally, you can have someking of ip pbx (softswitch) that does it and from sip's point of view is a back-to-back sip ua.
-- juha
At 04:55 PM 3/18/2003, Juha Heinanen wrote:
Daniel Sullivan writes:
Is it possible for SER to forward a call to another phone if the recipient does not answer?
It is easy if the on_no_response destination is not individualized, e.g., if any_username@iptel.org gets reforwarded to any_username@voicemail.iptel.org. That's what t_on_negative and reply_route ser script constructs are good for.
It is not easy know if the on_no_response addresses are individualized (e.g., jiri->1234, Dan->4321).
this could be achieved with sequential forking (by trying contacts in decreasing q order), but sequential forking is not yet supported in ser.
Serial forking as such is supported. The missing piece is (see above) keeping the individualized addresses, be it through user profile or multiple registrations with different q values. We will probably try to address it in overnext release; it will unfortunately not fit in the upcoming release.
-Jiri
-
Daniel Sullivan -
Greg Fausak -
Jiri Kuthan -
Juha Heinanen