Fixed Mobile Convergence

Fixed Mobile Convergence is latest telecommunication trend. It refers to convergence of Fixed and wireless telecommunication networks for seamless connectivity and optimized communication regardless of client location, phone number, handset and access network etc.

Business Need:

Rapid growth of wireless technologies such as Wifi, Wimax, EVDO & LTE has empowered users to lower their cellular and fixed line communication costs by using high-value IP based communication services. Now within the premises (Corporate Offices, homes, Malls & Hotels etc) users reap the benefits of cost effective IP based communication services over high speed wireless/fixed IP network and when moving outside the premises they usually have to switched back to their main cellular provider's network (GSM or 3G etc).

But residential users and enterprise workforce today need lot more flexibility on the go. They want to have seamless connectivity and service continuity while at the same time maintaining a single Phone Number, seamless convergence of multiple numbers, single voicemail, single bill and more. Fixed Mobile Convergence overcomes these evolving user needs and allows Communication Service Providers (CSPs) to offer superior customer experience.

AdvOSS Offering

AdvOSS delivers next generation infrastructure solution enabling CSPs to deploy and manage a SIP-based FMC (Fixed Mobile Convergence) service. It allows CSPs to provide superior customer experience and an exceptional flexibility to their end users by giving them a Converged Phone service, single voicemail box, single bill and ability to seamlessly move calls from their fixed line (SIP Phones/Dialers/PSTN numbers) to Cell Phones, wireless phones and IP Phones, or  the other way around whenever needed.

Solution Composition:

AdvOSS FMC Solution is based on following main products

  • AdvOSS Service Delivery Platform
  • SIP based FMC Application Server
  • Subscriber Self-Care portal
  • Core SBC Application
  • Converged B/OSS Products (CRM, Converged Billing, Charging & Rating Engine, Voucher Management, Franchisee Management & Provisioning Engine)

Solution description

This service groups together multiple fixed and mobile devices. Each device in the group acts as an alias to the each other device in the group. The devices could be an extension of a PBX or a subscriber’s individual landline or mobile phone. In both cases it works as follows:

Incoming Calls
Incoming calls to a phone are checked for aliases. In case aliases are present, the calls are sent to the called number and the aliases just like Follow Me/Find Me scenario, according to the sequential or parallel preference set at the FMC service level in subscriber’s profile. The default is to try the main extension as well as aliases in parallel.

Outgoing Calls
The simple case of outgoing calls deals with setting the Caller ID for each call made by a group member to any external destination. One of the group members can be set as the caller ID for all calls originating from a group member phone.

An advanced case of outgoing calls enables remote outgoing calling. In this case, one of the phone numbers in the FMC group is set as an access number for outgoing calls in the group. The subscriber dials the designated access number for the group from any other group member phone. The system recognizes the group member from the CallerID and automatically gives the user a new dial tone to dial out a destination number.

Network Diagram

{modal url=images/stories/fmc-outgoing-call.png} {/modal}

Click Image To Enlarge

Transferring calls between fixed and mobile

Subscriber initiated
The subscriber can switch calls using hot-keys between group members just like simple call transfer service available in a PBX.

System initiated (seamless)
An advanced form of this service (if enabled on the subscriber’s profile) allows the subscriber to automatically switch an ongoing call to a registered SIP phone line when the SIP device registers.

For example, an incoming call is sent in parallel to landline extension (a SIP Phone) and its mobile alias in the group but the landline extension is offline at the time. The call connects to the mobile and is still connected when the landline phone registers with the system. The system automatically transfers the call to landline without the calling party even noticing it.

Mobile dialers and other registered devices
This is an optional feature of FMC and can be used if the CSP chooses to provide mobile dialers for smart-phones or any other form of SIP based devices to their subscribers, in addition to the main registering device. In this case, each device, including the main one, registers with the same SIP URI and provides its own priority at the time of registration in standardized SIP parameters (q-parameter). This gives information to the system in the order of priority in which the devices have to be sent incoming calls in case multiple registrations are found.

This service enables one phone number use case for a subscriber as is very popular among next providers rolling our next generation services.

Subscriber initiated transfer works the same way as for the mobile phone case between multiple registered devices. This means the subscriber can transfer calls between multiple devices using hot-keys followed by a device priority. For example, a call is connected to a mobile dialer with priority 2. In the middle of the call, the subscriber wants to transfer to the main device with priority 1. He presses a hot-key followed by 1 to initiate the transfer.

AdvOSS Service Delivery Platform

FMC service is created and delivered on AdvOSS Service Delivery Platform. This platform is at the heart of all AdvOSS SIP based Application Services and is the core enabler for next generation services. SDP provides a run-time execution environment and a middleware for SIP application servers.

AdvOSS SDP is a Programmable, and Extensible Service Creation and Delivery Engine that enables the CSPs to develop and integrate new services at a brisk pace, as per their business requirements.

SDP has been built from the ground up to enable third party developers to build and deploy feature rich SIP applications using Call Control XML (CCXML). CCXML provides simple primitives, allowing users to write applications enabling them to quickly transform ideas to solutions.

AdvOSS platform extends CCXML to support primitives for Authentication, Authorization and Accounting (AAA), database access and several others allowing applications to interface with billing systems either directly or through Radius and Diameter protocols.

Supported SIP RFCs

  • RFC 3261
  • RFC 3263
  • RFC 3264
  • RFC 3265
  • RFC 4566
  • RFC 3550
  • RFC 3903
  • RFC 3262
  • RFC 4694
  • RFC 3966
  • RFC 5547
  • RFC 3455
  • RFC 3680
  • RFC 4346

In addition, SDP provides several key services for successful service deliver. Some of these include:

  • High Availability and Automatic IP Takeover based Fault tolerance
  • Comprehensive Event logging and Reporting
  • Alerting and notifications
  • XML and HTTP based API interfaces with external applications
  • CDR generation
  • Session Monitoring and Debugging
  • Database Connectivity
  • AAA client functionality for both prepaid and postpaid scenarios
  • Unlimited scalability via SIP load balancing and distributed processing
  • Congestion Control on SIP ingress traffic
More information on SDP can be found at:

Contact Now!

Tel: +1 (416) 900 5593

Suite 401, 50 Burnhamthorpe Road W.
Mississauga, ON L5B 3C2, Canada