Browse Prior Art Database

MULAP Feature for SIP-endpoints

IP.com Disclosure Number: IPCOM000019965D
Published in the IP.com Journal: Volume 3 Issue 11 (2003-11-25)
Included in the Prior Art Database: 2003-Nov-25
Document File: 2 page(s) / 106K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

Modern communication networks offer many features to their subscribers. One of these features can be the Request For Comment (RFC), for example. Like others it is based on the Session Initiation Protocol (SIP) in accordance with the standard RFC3261 by the Internet Engineering Task Force (IETF). In contrast to non-SIP-phones the SIP-endpoints (phones or software-clients connected to an Internet Protocol based network via SIP-signaling) have not been able to use any MULAP (Multiple Line Appearance) -functionality so far. The following text outlines a method to transport a MULAP-functionality, the so called 'Buddy Group' feature, to a SIP-platform. A Buddy Group is a collection of subscribers. Calls made to the group (by calling the group number) are signaled to all members. Similarly, when group members make calls to a subscriber who is not member of the group, the calling party can choose if the called party will be informed about the group number or about the individual number. Furthermore, the group members have additional capabilities to handle intra-group calls like call transfer, call hold, bridging, etc.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

S

© SIEMENS AG 2003 file: 2003J13433.doc page: 1

MULAP Feature for SIP-endpoints

Idea: Bart Reynaert, BE-Gent; Jan Vrolix, BE-Gent; Kaatje Coenen, BE-Gent;

Roger Lybeer, BE-Gent; Bettina Schelfhout, BE-Gent; Michel Lambrecht, BE-Gent

Modern communication networks offer many features to their subscribers. One of these features can be the Request For Comment (RFC), for example. Like others it is based on the Session Initiation Protocol (SIP) in accordance with the standard RFC3261 by the Internet Engineering Task Force (IETF). In contrast to non-SIP-phones the SIP-endpoints (phones or software-clients connected to an Internet Protocol based network via SIP-signaling) have not been able to use any MULAP (Multiple Line Appearance) -functionality so far. The following text outlines a method to transport a MULAP- functionality, the so called 'Buddy Group' feature, to a SIP-platform.

A Buddy Group is a collection of subscribers. Calls made to the group (by calling the group number) are signaled to all members. Similarly, when group members make calls to a subscriber who is not member of the group, the calling party can choose if the called party will be informed about the group number or about the individual number. Furthermore, the group members have additional capabilities to handle intra-group calls like call transfer, call hold, bridging, etc.

The new feature is network-based with a centralized feature control via a SIP proxy server or a Buddy Group server, respectively (cf. Fig. 1). It is not restricted to use within an enterprise environment and could be deployed in the public internet (Application Service Provider ASP). The SIP protocol (RFC3261) is extended to carry additional signaling information, like call status of the group members. The internal software structure is shown in Fig. 2. SIP-endpoints wh...