Call coverage is the treatment if the called party doesn't answer. Ex:
Avaya x111 calls avaya x222. x222 is not available and the call proceeds to voice mail. Voice mail is a SipX server, but I need to get the call there through a logical conduit (say x333 which will be the same for everyone). I don't want SipX to point me to a mailbox for x333, but rather the original called party x222. Is this possible in SipX? Tom Funk Sr. Engineer Converged Networking,CTI 303.737.4747 ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Josh Patten Sent: Wednesday, May 05, 2010 9:44 AM To: [email protected] Subject: Re: [sipx-users] SipX call coverage from Avaya S87XX Define call coverage... Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 5/5/2010 10:43 AM, Funk, Tom wrote: Is there a way to set call coverage from Avaya to SipX voice mail while retaining the RDNIS? We did this in Asterisk by designating the RDNIS in the History Info as a variable and adding it to the context. Is there any way to do something similar in SipX? Even so, I assume that the message waiting light wouldn't work since Avaya phones won't accept the SIP notify message unless we registered it to the SES (and subsequently lose Avaya features). Correct? TIA Tom Funk Sr. Engineer Converged Networking,CTI 303.737.4747 ________________________________ The information contained in this message and any accompanying attachments may contain privileged, private and/or confidential information protected by state and federal law. Penalties may be assessed for unauthorized use and/or disclosure. This message and any attachments are intended for the designated recipient only. If you have received this information in error, please notify the sender immediately and return or destroy the information. This e-mail transmission and any attachments are believed to have been sent free of any virus or other defect that might affect any computer system into which it is received and opened. It is, however, the recipient's responsibility to ensure that the e-mail transmission and any attachments are virus free, and the sender accepts no responsibility for any damage that may in any way arise from their use. _______________________________________________ sipx-users mailing list [email protected]<mailto:[email protected]> List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ ________________________________ The information contained in this message and any accompanying attachments may contain privileged, private and/or confidential information protected by state and federal law. Penalties may be assessed for unauthorized use and/or disclosure. This message and any attachments are intended for the designated recipient only. If you have received this information in error, please notify the sender immediately and return or destroy the information. This e-mail transmission and any attachments are believed to have been sent free of any virus or other defect that might affect any computer system into which it is received and opened. It is, however, the recipient's responsibility to ensure that the e-mail transmission and any attachments are virus free, and the sender accepts no responsibility for any damage that may in any way arise from their use.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
