IMS-Communicator-开源

  • L6_317500
    了解作者
  • 5.9MB
    文件大小
  • zip
    文件格式
  • 0
    收藏次数
  • VIP专享
    资源类型
  • 0
    下载次数
  • 2022-05-13 10:31
    上传日期
IMS-Communicator 是一个基于旧版 sip-communicator java 项目的 IMS 软电话,在 JAIN-SIP 堆栈和 Java Media Framework API 之上实现。 它可以与 Open IMS Core (http://www.openimscore.org) 一起使用。
ims-communicator-windows-release-070605.zip
  • ims-communicator
  • log
  • ims-communicator.app.log
    0B
  • resource
  • sip-communicator.jpg
    2.2KB
  • default-icon.jpg
    3.1KB
  • presence-icon.jpg
    2.8KB
  • sip-communicator-icon-16x16.jpg
    915B
  • sip-communicator.logo.jpg
    3KB
  • presence-icon-16x16.jpg
    21.9KB
  • ims-comm_icon-16x16.jpg
    22.3KB
  • default-logo.jpg
    40.5KB
  • jmf.jpg
    1.4KB
  • lib
  • jmh263enc.dll
    104KB
  • jmam.dll
    52KB
  • jmacm.dll
    48KB
  • jmvfw.dll
    44KB
  • jmh261.dll
    276KB
  • jmdaud.dll
    40KB
  • jmdaudc.dll
    28KB
  • jmmpa.dll
    372KB
  • jmvcm.dll
    36KB
  • jmg723.dll
    96KB
  • jmmci.dll
    28KB
  • jmjpeg.dll
    140KB
  • jmutil.dll
    72KB
  • jmgsm.dll
    56KB
  • jmvh263.dll
    180KB
  • jmddraw.dll
    32KB
  • jmfjawt.dll
    32KB
  • jsound.dll
    404KB
  • soundbank.gm
    1.1MB
  • jmmpegv.dll
    76KB
  • jmgdi.dll
    36KB
  • jmcvid.dll
    48KB
  • sound.jar
    287.2KB
  • ims-communicator-config.bat
    184B
  • dialhistory.txt
    0B
  • ims-communicator.jar
    1.9MB
  • ims-communicator.bat
    172B
  • contact-list.xml
    107B
  • README.txt
    15.9KB
  • jmf.jar
    2MB
  • ims-communicator.xml
    7.3KB
内容介绍
Portugal Telecom Inovação IMS-Communicator Documentation last update: 2007-02-15 Introduction 1 Requirements 3 IMS-Communicator Features 3 Standards support list 3 Supported features list 3 IMS-Communicator Roadmap 3 Repository 4 JMF binaries 4 Binary releases 4 Configuration 5 How to 7 How to compile 7 How to run 7 How to configure the SIP profile 7 How to configure a webcam 7 How to place a call 8 How to make a SIP call transfer 9 How to enable the contact-list 9 How to enable the Peer-to-Peer mode 10 FAQ 11 Software Licence 11 Introduction IMS-Communicator is a SIP softphone based on the old version of the sip-communicator java project (http://sip-communicator.org/), implemented on top of the JAIN-SIP stack (https://jain-sip.dev.java.net/) and the Java Media Framework API (http://java.sun.com/products/java-media/jmf/). Some changes have been made to the JAIN-SIP stack to support IMS, such as new SIP headers and SDP functionalities, contribution that have been submitted to the community and is already shipped within the latest JAIN-SIP stack. Originally, the SIP-Communicator client supported normal SIP registration of one public user identity, voice and video session initiation, and some IM functionality, on Windows and Linux. The main IMS User Equipment (UE) procedures were then implemented, as described in the 3GPP specifications TS 24.229, TS 23.228 and others (check http://www.tech-invite.com/ for IMS call flows examples). Some of the IMS functionalities implemented include IMS Registration (Authorization, Security Agreement and Subscription to the reg event package), IMS session initiation (PRACK, UPDATE and Precondition Mechanism) and Call Transfer. At this point, the IMS-Communicator has several limitations, including the following: ? provided support for only one public user identity ? user not able to access the IMS network anonymously ? When placing a call, resources for the media session are considered as available Requirements ? JRE 1.5 (or J2DK 1.5 to compile the project) ? Java Media Framework (JMF) API (optional – already shipped with IMS-Communicator) ? Apache Ant (to compile the project) IMS-Communicator Features Standards support list ? SIP and SDP support (modified JAIN-SIP stack to support IMS) ? Procedures at the UE (SIP and SDP) – 3GPP TS 24.229 ? SIP PRACK method (RFC 3262) ? SIP UPDATE method (RFC 3311) ? SIP Precondition Mechanism (RFC 3312 + RFC 4032) ? A SIP Event Package for Registrations (RFC 3680) ? SIP Security Agreement (RFC 3329 + 3GPP TS 33.203 Annex H) ? SIP REFER method (RFC 3515) and Session Transfer Procedures (3GPP TS 23.228) ? SIP Referred-By Mechanism (RFC 3892) ? 3GPP TS 24.229 – IP multimedia call control protocol based on SIP and SDP ? HTTP AKA (RFC 3310) ? HTTP Digest Authentication (RFC 2617) ? MILENAGE 3GPP Authentication Algorithm (TS 35.205, TS 35.206, TS 35.207, TS 35.208) Supported features list ? Setup wizard ? IMS user Registration and Authentication (AKAv1-MD5) ? IMS Call Initiation ? Voice and video calls ? JMF 2.1.1 - Supported Formats – http://java.sun.com/products/java-media/jmf/2.1.1/formats.html ? SIP Call Transfer (Blind and Consultative Transfer) ? Dial history ? Contact list, IM and Presence support IMS-Communicator Roadmap ? Full HTTP AKA support (SQN synchronization) ? Early Media (RFC 3959, RFC 3960) Repository The IMS-Communicator sources, binary releases and documentation can be obtained from http://imscommunicator.berlios.de. The project can be checked out through anonymous (svnserve) SVN with the following instruction set. • svn checkout svn://svn.berlios.de/imscommunicator/trunk/ims-communicator The project can also be checked out through anonymous HTTP with the following instruction set. • svn checkout http://svn.berlios.de/svnroot/repos/imscommunicator/trunk/ims-communicator The folder svn.berlios.de/imscommunicator/trunk/ims-communicator contains the Java sources which are bundled within an Eclipse project. It also contains the required libraries (including the modified JAIN-SIP stack), exception made for the JMF binaries which are system dependent and increase heavily the project weight. JMF binaries For that reason the JMF binaries are distributed as a separated package, available at the folder <lib> in the repository svn.berlios.de/imscommunicator/trunk/. They are also available as compressed *.rar files. There’s support for Linux, Windows and Solaris (Solaris JMF package not included – contact us if you are interested). So, download the one you aim and place it in the lib folder inside the IMS-Communicator project. Binary releases For your convenience, there are binary releases of the IMS-Communicator available at the folder <releases> in the repository svn.berlios.de/imscommunicator/trunk/. Configuration The configuration of the IMS-Communicator is done manually in the ims-communicator.xml file or by the menu Settings > Configure at the UA GUI. Featured next, some explanation of the configuration properties: <net.java.sip.communicator> - general sip-communicator properties ? FIRST_LAUNCH – “true” for the execution of the configuration wizard in the first launch of the UA ? ENABLE_SIMPLE – “true” to enable presence with peer contacts <net.java.sip.communicator.media> - media and SDP options ? PREFERRED_AUDIO_ENCODING – number of the preferred audio codec, from the audio codecs supported by JMF ? PREFERRED_VIDEO_ENCODING – number of the preferred video codec, from the video codecs supported by JMF ? MEDIA_SOURCE – path to the media source to be sent ? AUDIO_PORT – port where to receive incoming audio data ? VIDEO_PORT – port where to receive incoming video data <net.java.sip.communicator.sip> - SIP profile configuration ? PUBLIC_ADDRESS – SIP public user identity ? TRANSPORT – transport protocol used by the client. UDP by default if none configured ? REGISTRAR_ADDRESS – domain name of the SIP Registrar ? USER_NAME – user name, used to save the user credentials ? STACK_PATH – SIP stack, NIST-SIP by default (“gov.nist”) ? PREFERRED_LOCAL_PORT – if none configured or port already in use, other will be generated ? DISPLAY_NAME – SIP display-name, to be included in the headers From, To and Contact ? REGISTRAR_TRANSPORT – transport protocol used by the SIP Registrar ? REGISTRATIONS_EXPIRATION – timeout for the user registration ? REGISTRAR_PORT – SIP Registrar’s port value ? DEFAULT_DOMAIN_NAME – IMS home network domain name ? DEFAULT_AUTHENTICATION_REALM – realm parameter used in the Authentication header <net.java.sip.communicator.sip.ims> - IMS configuration ? IMS_CLIENT – “true” if IMS procedures to be used at registration and session initiation ? PRIVATE_ADDRESS – User private address for authentication ? PREFERRED_ADDRESS – SIP address to be include in the P-Preferred-Identity header ? PREFERRED_DISPLAY_NAME – optional display name to be include in the P-Preferred-Identity header ? PRIVACY – value to be included in the Privacy header ? OPERATOR_ID – operator ID (32 HEX char). Default is all zeros ? SECURITY_AGREEMENT – value of the security mechanism parameter. If empty, Security-Client header is not sent ? SECURITY_ALGORITHM – Algorithm parameter in the Security-Client header ? if security mechanism equals “ipsec-3gpp”, the following properties are relevant: ? SECURITY_ENCRYPT_ALG – Encryption Algorithm parameter in the Security-Client header ? SECURITY_SPI_C – SPI-Client parameter in the Security-Client header ? SECURITY_SPI_S – SPI-Server parameter in the Security-Client header ? SECURITY_PORT_C – Client Port parameter in the Security-Client header ? SECURITY_PORT_S – Server Port parameter in the Security-Client header ? ACCEPT_REFER_WITHOUT_SESSION_ON – accept REFER request from a peer even if a session is established with that peer ? PCSCF_DYNAMIC_DISCOVERY – SIP
评论
    相关推荐