IP Library Granted Patent US 9,860,383
Granted Patent B2
US 9,860,383 · App. 14/225,253 · Granted Jan 2, 2018

Method and apparatus for managing voicemail in a communication session

Inventors: John Albert (Kanata, CA); Jianqi (Jerry) Yin (Ottawa, CA); Kavita Jain (Nepean, CA); Liang Zhou (Kanata, CA); Thomas Gray (Mansfield, CA)
Assignee: Mitel Networks Corporation
H04M3/53366
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,860,383
App. No.
14/225,253
Granted
Jan 2, 2018
Kind
B2
Abstract

A system, method and apparatus for managing voicemail in a communication session between a sending communication device and a receiving communication device are provided. It is determined at the receiving communication device that a voicemail is to be created. The voicemail based on content received via the sending communication device. The voicemail is recorded. The voicemail is caused to be stored at resources associated with the sending communication device.

Claims (31)

1. A method for managing voicemail in a communication session between a sending communication device and a receiving communication device, comprising;

determining, at the receiving communication device, that a voicemail is to be created, said voicemail based on content received via the sending communication device;

in response to a determination that the voicemail from the sending communication device is to be created, retrieving a policy for storing the voicemail wherein the policy includes a white list of identifiers of sending communication devices for which the receiving device is authorized to create and store the voicemail at resources associated with the receiving communication device, a black list of identifiers of sending communication devices for which voicemails are not authorized to be created, and a grey list of identifiers of sending communication devices for which the receiving communication device is authorized to create voicemails, but wherein storing said voicemail occurs at resources associated with the sending communication device;

if the sending communication device is not on the black list, recording said voicemail; and

if the sending communication device is on the grey list, causing said voicemail to be stored at resources dedicated to storing said voicemail on behalf of the sending communication device,

wherein a decision on where to store said voicemail made according to said policy.

2. The method of claim 1 wherein causing said voicemail to be stored at said resources associated with the sending communication device occurs only if said policy indicates that said voicemail is to be stored at said resources associated with the sending communication device.

3. The method of claim 1 , wherein said policy is stored at the receiving communication device and said decision on where to store said voicemail is made at the receiving communication device.

4. The method of claim 1 , wherein the sending communication device is identified by blocked caller ID information and said voicemail is treated as if the identifier of the sending communication device is on one of said black list or said grey list.

5. The method of claim 1 , wherein said policy comprises at least one of a null policy and a resiliency policy, said null policy indicative that said voicemail to be stored at resources associated with the sending communication device, and said resiliency policy comprising a list of resources where said voicemail is to be stored, such that said voicemail is stored in more than one location.

6. The method of claim 5 , wherein said resiliency policy is customizable for at least one of the receiving communication device and a user associated with the receiving communication device.

7. The method of claim 5 , further comprising retrieving said resiliency policy from a managing device and said resiliency policy comprises identifiers of resources where said voicemail is to be stored.

8. The method of claim 1 , further comprising negotiating where said storing said voicemail is to occur, based on said policy, said negotiating occurring between the sending communications device and the receiving communications device.

9. The method of claim 1 , wherein said sending communication device is enabled for at least one of modification and deletion of said voicemail after said storing said voicemail at said resources associated with said sending communication device.

10. The method of claim 1 , further comprising notifying the receiving communication device that said voicemail is available for retrieval once said voicemail is stored.

11. The method of claim 1 , wherein said recording occurs at resources associated with said receiving communication device to create a voicemail file, and said causing said voicemail to be stored at resources associated with the sending communication device occurs by transmitting said voicemail file to said sending communication device.

12. The method of claim 11 , wherein said sending communication device determines where said voicemail file is to be stored upon receiving said voicemail file.

13. A communication device for managing voicemail in a communication session between the communication device and a sending communication device, comprising,

a communication interface for communicating with the sending communication device; and

a processing unit enabled for performing the method according to claim 1 .

14. A method for managing voicemail in a communication session between a sending communication device and a receiving communication device, comprising;

determining, at the receiving communication device, that a voicemail is to be created, said voicemail based on content received via the sending communication device;

in response to a determination that a voicemail from the sending communication device is to be created, retrieving a policy for storing said voicemail, and if the voicemail is to be created, creating the voicemail and performing a decision on where to store said voicemail made according to said policy; and

causing said voicemail to be stored at resources dedicated to storing said voicemail on behalf of the sending communication device,

wherein said policy comprises a null policy and a resiliency policy, said null policy automatically causing said voicemail to be stored at resources associated with the sending communication device, and said resiliency policy comprising a list of resources where said voicemail is to be stored, such that said voicemail is stored in more than one location, said resiliency policy is customizable for at least one of the receiving communication device and a user associated with the receiving communication device

wherein the policy further includes a white list of identifiers of sending communication devices for which the receiving device is authorized to create and store the voicemail at resources associated with the receiving communication device, a black list of identifiers of sending communication devices for which voicemails are not authorized to be created, and a grey list of identifiers of sending communication devices for which the receiving communication device is authorized to create voicemails, but wherein storing said voicemail occurs at resources associated with the sending communication device.

15. The method of claim 14 , further comprising retrieving said resiliency policy from a managing device and said resiliency policy comprises identifiers of resources where said voicemail is to be stored.

16. A communication device for managing voicemail in a communication session between the communication device and a sending communication device, comprising,

a communication interface for communicating with the sending communication device; and

a processing unit enabled for performing the method according to claim 14 .

17. The method of claim 14 , further comprising negotiating where said storing said voicemail is to occur, based on said policy, said negotiating occurring between the sending communications device and the receiving communications device.

Assignments (17)
SECURITY INTEREST Recorded Jun 30, 2025
From: MLN US HOLDCO LLC; MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: U.S. PCI SERVICES, LLC
Reel/Frame 071758/0843 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: ACQUIOM AGENCY SERVICES LLC
To: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071730/0632 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: ANKURA TRUST COMPANY, LLC
To: MITEL (DELAWARE), INC.; MITEL COMMUNICATIONS, INC.; MITEL CLOUD SERVICES, INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071722/0721 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MITEL (DELAWARE), INC.; MITEL COMMUNICATIONS, INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071712/0821 →
SECURITY INTEREST Recorded Jun 20, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 071676/0815 →
SECURITY INTEREST Recorded Mar 12, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 070689/0857 →
NOTICE OF SUCCCESSION OF AGENCY - 2L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069896/0001 →
NOTICE OF SUCCESSION OF AGENCY - 4L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ANKURA TRUST COMPANY, LLC
Reel/Frame 069896/0827 →
NOTICE OF SUCCESSION OF AGENCY - 5L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ANKURA TRUST COMPANY, LLC
Reel/Frame 069897/0046 →
NOTICE OF SUCCCESSION OF AGENCY - PL Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069895/0755 →
NOTICE OF SUCCCESSION OF AGENCY - 3L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 070006/0268 →
SECURITY INTEREST Recorded Oct 31, 2022
From: MITEL NETWORKS CORPORATION
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 061824/0282 →
SECURITY INTEREST Recorded Dec 7, 2018
From: MITEL NETWORKS ULC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047741/0674 →
SECURITY INTEREST Recorded Dec 7, 2018
From: MITEL NETWORKS ULC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047741/0704 →
RELEASE OF SECURITY INTEREST Recorded Dec 3, 2018
From: CITIZENS BANK, N.A.
To: MITEL NETWORKS CORPORATION
Reel/Frame 048096/0785 →
SECURITY INTEREST Recorded Mar 23, 2017
From: MITEL NETWORKS CORPORATION
To: CITIZENS BANK, N.A.
Reel/Frame 042107/0378 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 11, 2015
From: ALBERT, JOHN; YIN, JIANQI (JERRY); JAIN, KAVITA; ZHOU, LIANG; GRAY, THOMAS
To: MITEL NETWORKS CORPORATION
Reel/Frame 035011/0001 →
Continuity (3)
Continuation 12316484 · Dec 12, 2008
Related Publication 20150281457A1 · Oct 1, 2015
Related Publication 20170180556A9 · Jun 22, 2017