HP | iPAQ 512 Voice Messenger | User guide | HP iPAQ 512 Voice Messenger User's Guide

Voice over IP (VoIP) Application Note
HP iPAQ 500 series Voice Messenger
The goal of this document is to clearly and concisely state what HP iPAQ 500 series
Voice Messenger is and is not capable of supporting for mobile IP telephony, aka VoIP,
or Voice over IP. All the capabilities and interoperability scenarios haven’t been tested at
this point, and until then this document will be a work-in-progress. As new information
becomes available, it will be added to this document.
Contents
1
2
3
4
5
6
7
Overview..................................................................................................................... 2
Media and Signaling Protocols ................................................................................... 3
Telephony Features..................................................................................................... 3
Audio Quality.............................................................................................................. 4
Hardware and Firmware ............................................................................................. 5
WLAN Infrastructure.................................................................................................. 6
IP-PBX and SIP Server Support ................................................................................. 6
7.1 Compatibility with Cisco unified Call Manager v5.1 .......................................... 7
7.2 Compatibility with Avaya Communication Manager v4.0 / SES v3.1.2 ............. 8
7.3 Compatibility with Nortel MCS 5100 v4.5 .......................................................... 9
7.4 Compatibility with Nortel CS1000 v4.5 ............................................................ 10
7.5 Compatibility with Alcatel OmniPCX Enterprise v6.1...................................... 11
8
Accessory Support .................................................................................................... 12
9
Configuring VoIP...................................................................................................... 12
9.1 Enabling ‘Internet Calling’................................................................................. 12
9.2 Checking Wi-Fi .................................................................................................. 12
9.3 Using HP iPAQ Setup Assistant ........................................................................ 12
9.4 VoIP Dial Plan ................................................................................................... 14
9.4.1 IMPORTANT NOTE ABOUT EMERGENCY CALLING ...................... 14
9.5 ADDITIONAL CONFIGURATION ................................................................. 16
10 Appendix A – Standards Support ............................................................................. 17
10.1
Signaling Standards Implemented .................................................................. 17
10.2
Media/Other Standards ................................................................................... 18
10.3
Standards Not Implemented ........................................................................... 18
1
Overview
Mobile IP telephony services can be separated into three broad categories, each with its
own specific target markets and technologies used. These categories are illustrated below:
Tested use cases for the built-in VoIP client on the HP iPAQ 500 series smartphone cover
the enterprise VoIP segment exclusively and expect the enterprise has IT staff that
manage their own IP-PBX systems and provision devices for enterprise users. Mobile
enterprise VoIP services should be accessible anywhere the VoIP-enabled enterprise
wireless local area network (WLAN) provides coverage, typically within company
buildings and possibly around corporate campuses. Using the built-in VoIP client for
mobile access to the company’s IP-PBX from remote locations (homes, hotels, Internet
hotspots, etc.) is not a supported capability.
HP uses the native Microsoft SIP (Session Initiation Protocol) client in Windows Mobile
6 to access VoIP services, and this SIP client’s capabilities and limitations have been
further split into the following categories for the purposes of this document:


Media and Signaling Protocols
Telephony Features





Audio Quality
Hardware and Firmware
WLAN Infrastructure
IP-PBX and SIP Server Support
Accessory Support
While Internet voice services delivered by Internet Telephony Service Providers (ITSPs)
may also be based on SIP, HP has done no testing or validation of interoperability with
these services at this time.
2 Media and Signaling Protocols
This category is related to the industry protocols that exist today for carrying control
messages and media messages.
Supported:


SIP – Session Initiation Protocol for Signaling [RFC 3261]
G.711 – Audio codec for compression/decompression of voice. Both A-law and
u-law variants are included.
Not Supported:




H.323 – signaling protocol used in some IP-PBXs
SCCP – Cisco’s proprietary call control protocol for Unified CallManager.
G.729 – Compressed audio codec more suitable for voice over WLAN compared
to G.711
Secure RTP [SRTP] – secure version of the RTP protocol [RFC 3711]
A full list of the standards supported and not supported is included in Appendix A of this
document.
3
Telephony Features
This category is related to the standard telephony features available in a VoIP
implementation.
Supported:












Originate and Terminate Calls
Caller ID
Call Waiting
Call Hold
Call Mute
Call Forwarding
*only with a SIM card present
o The number the call is forwarded to must be in a format [E.164] that can
be validated on the GSM network.
Configuring Caller ID
*only with a SIM card present
Configuring Call Waiting
*only with a SIM card present
Call Barring
*only with a SIM card present
Blind Transfer
In-Band and out-of-band DTMF
o Out-of-band DTMF is requested by default. If the other end-point
declines, in-band DTMF is used.
Emergency Calling (over GSM only)
Interoperability testing with SIP-enabled IP PBX systems is being done to confirm
feature functionality with each vendor’s SIP implementation. Refer to subsequent
sections of this document for test results.
Not Supported:





Conferencing a second line
Consultative Transfer
Call Park/Pick-up
‘Do Not Disturb’
Emergency Calling over IP
A full list of the RFCs supported and not supported is included in Appendix A of this
document.
4
Audio Quality
This category is related to the components that need to be in the device to handle audio
quality.
Supported:

Automatic Gain Control





5
Adaptive Jitter Buffer Management
Voice Activity Detection
Silence Suppression
Comfort Noise Generation
Acoustic Echo Cancellation (3rd party sourced, not provided by Microsoft)
Hardware and Firmware
This category is related to WLAN and other hardware/firmware components in the
handset that are critical to the performance and usability of VoIP.
Supported:



802.11b/g
802.11i (PEAPv0 and EAP-TLS with certificates)
Encryption suites: WEP64, WEP128, TKIP and AES CCMP
Not Supported:

Full 802.1X Supplicant – Microsoft provides the limited set of EAP
authentication noted above. Additional EAP methods may be required by some
customers.
*A 3rd party supplicant is currently under
consideration for a future release

Fast Roaming – A basic roaming agent has been implemented, and specific
roaming performance results will be published when they become available.
802.11r “Fast Roaming” is currently unsupported.
*Fast roaming enhancements are under
consideration for a future release

Cisco Compatible Extensions (CCX) – The WLAN module firmware and driver
would have to be updated to support the CCX v4 ASD feature set.
*A CCX v4 implementation is currently
under consideration for a future release

Certain features of 802.11e [WMM] are not currently supported.
o Automatic Power Save Delivery (APSD) and Unscheduled Automatic
Power Save Delivery (U-APSD) power saving mechanisms are not
currently supported.
o Even though packet tagging [802.1p and Diffserv] is inherently supported
by Windows Mobile 6, there may not be any benefit by tagging voice
packets with a higher priority.
6
WLAN Infrastructure
This category is related to the wireless local area network (WLAN) infrastructure to
which the handset connects to send and receive IP traffic. The key consideration from the
mobile handset perspective is typically AP-AP roaming. Given the real time requirements
of voice and the delays inherent in WLAN authentication (802.11i), the strongly
recommended answer is a VoIP-enabled pervasive enterprise WLAN infrastructure. Note
that HP Services has a well-developed practice for migrating customers’ WLANs to this
model. The baseline requirement here is a controller-based AP deployment; not
standalone APs. Examples of these controller-based WLAN product offerings include:
•
•
•
•
•
Cisco Aironet APs with Wireless LAN controller(s)
HP ProCurve Radio Ports plus Wireless Edge Services xl module(s) in 5300xl
switch chassis
Extreme Networks Altitude APs and Summit switches
Aruba Networks APs and Mobility Controller(s)
Meru Networks APs and Controller(s)
Testing is underway with Cisco Aironet APs and wWireless LAN controllers. Other
WLAN infrastructure testing and results may be available in the future.
For optimal performance, all 802.11b and 802.11g data rates should be enabled on the
APs. Limiting the data rates on the APs may prevent iPAQ 500 series devices from
connecting to the AP.
7
IP-PBX and SIP Server Support
This category is related to the SIP-based IP-PBX system or server with which the
handheld device must interact for VoIP services. HP testing is underway with enterprise
IP-PBX products from Cisco, Avaya, Alcatel, and Nortel. Detailed test criteria and results
will be added to this section as they become available.
Results of other additional testing with operator-class SIP servers (Broadsoft, Sylantro,
Huawei, Alcatel, etc.) will be included when they are made available to HP.
7.1 COMPATIBILITY WITH CISCO UNIFIED CALL MANAGER V5.1
Feature
Brief Description
Pass/Fail Comments
Originate Calls
SIP End Point to End point,
Extension, and PSTN
From SIP End Point, Extension,
and PSTN
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
Call Forward All (CFA), Busy
(CFB) and Not Answered
(CFNA)
Voicemail notification passed
from server to Endpoint
Pass
Originator and Terminator
transfer to Endpoint, Extension
and PSTN
On Originator and Terminator,
waiting, timeout, release before
answer
Calling Line ID Presentation
(CLIP) Type I and II
Calling Line ID Restriction
(CLIR)
DID from Endpoint to Local and
Remote Extension and PSTN to
Endpoint
Originator and Terminator hold
and resume with Endpoint,
Extension, and PSTN
Pass
Terminate Calls
DTMF (in-band)
DTMF (RFC 2833)
Call Forward
Message Waiting
Indicator
Blind Transfer
Call Waiting
Caller ID
Call Barring
Direct Inward Dial
Call Hold
(Music on Hold)
Pass
Pass
Pass
Pass
Fail
Requires SIM card and
accepts valid E.164
numbers only
Cisco uses SIP Notify,
Enhancement request
submitted to Microsoft
Pass
Requires SIM card to
configure
Pass
Requires SIM card to
configure
Requires SIM card to
configure
Pass
Pass
Pass
7.2 COMPATIBILITY WITH AVAYA COMMUNICATION MANAGER V4.0 / SES
V3.1.2
Feature
Brief Description
Originate Calls
SIP End Point to End point,
Extension, and PSTN
From SIP End Point, Extension,
and PSTN
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
Call Forward All (CFA), Busy
(CFB) and Not Answered
(CFNA)
Voicemail notification passed
from server to Endpoint
Originator and Terminator
transfer to Endpoint, Extension
and PSTN
On Originator and Terminator,
waiting, timeout, release before
answer
Calling Line ID Presentation
(CLIP) Type I and II
Calling Line ID Restriction
(CLIR)
DID from Endpoint to Local and
Remote Extension and PSTN to
Endpoint
Originator and Terminator hold
and resume with Endpoint,
Extension, and PSTN
Terminate Calls
DTMF (in-band)
DTMF (RFC 2833)
Call Forward
Message Waiting
Indicator
Blind Transfer
Call Waiting
Caller ID
Call Barring
Direct Inward Dial
Call Hold
(Music on Hold)
Pass/Fail Comments
Testing still in progress
7.3 COMPATIBILITY WITH NORTEL MCS 5100 V4.5
Feature
Brief Description
Pass/Fail Comments
Originate Calls
SIP End Point to End point,
Extension, and PSTN
From SIP End Point, Extension,
and PSTN
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
Call Forward All (CFA), Busy
(CFB) and Not Answered
(CFNA)
Voicemail notification passed
from server to Endpoint
Originator and Terminator
transfer to Endpoint, Extension
and PSTN
On Originator and Terminator,
waiting, timeout, release before
answer
Calling Line ID Presentation
(CLIP) Type I and II
Calling Line ID Restriction
(CLIR)
DID from Endpoint to Local and
Remote Extension and PSTN to
Endpoint
Originator and Terminator hold
and resume with Endpoint,
Extension, and PSTN
Pass
Terminate Calls
DTMF (in-band)
DTMF (RFC 2833)
Call Forward
Message Waiting
Indicator
Blind Transfer
Call Waiting
Caller ID
Call Barring
Direct Inward Dial
Call Hold
(Music on Hold)
Pass
Pass
Pass
Pass
Requires SIM card and
accepts valid E.164
numbers only
Pass
Pass
Pass
Requires SIM card to
configure
Pass
Requires SIM card to
configure
Requires SIM card to
configure
Pass
Pass
Pass
.
7.4 COMPATIBILITY WITH NORTEL CS1000 V4.5
Feature
Brief Description
Originate Calls
SIP End Point to End point,
Extension, and PSTN
From SIP End Point, Extension,
and PSTN
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
Call Forward All (CFA), Busy
(CFB) and Not Answered
(CFNA)
Voicemail notification passed
from server to Endpoint
Originator and Terminator
transfer to Endpoint, Extension
and PSTN
On Originator and Terminator,
waiting, timeout, release before
answer
Calling Line ID Presentation
(CLIP) Type I and II
Calling Line ID Restriction
(CLIR)
DID from Endpoint to Local and
Remote Extension and PSTN to
Endpoint
Originator and Terminator hold
and resume with Endpoint,
Extension, and PSTN
Terminate Calls
DTMF (in-band)
DTMF (RFC 2833)
Call Forward
Message Waiting
Indicator
Blind Transfer
Call Waiting
Caller ID
Call Barring
Direct Inward Dial
Call Hold
(Music on Hold)
Pass/Fail Comments
Testing still in progress
7.5 COMPATIBILITY WITH ALCATEL OMNIPCX ENTERPRISE V6.1
Feature
Brief Description
Pass/Fail Comments
Originate Calls
SIP End Point to End point,
Extension, and PSTN
From SIP End Point, Extension,
and PSTN
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
SIP End Point, Extension,
and PSTN send and receive
DTMF tones
Call Forward All (CFA), Busy
(CFB) and Not Answered
(CFNA)
Voicemail notification passed
from server to Endpoint
Originator and Terminator
transfer to Endpoint, Extension
and PSTN
On Originator and Terminator,
waiting, timeout, release before
answer
Calling Line ID Presentation
(CLIP) Type I and II
Calling Line ID Restriction
(CLIR)
DID from Endpoint to Local and
Remote Extension and PSTN to
Endpoint
Originator and Terminator hold
and resume with Endpoint,
Extension, and PSTN
Pass
Terminate Calls
DTMF (in-band)
DTMF (RFC 2833)
Call Forward
Message Waiting
Indicator
Blind Transfer
Call Waiting
Caller ID
Call Barring
Direct Inward Dial
Call Hold
(Music on Hold)
Pass
Pass
Pass
Pass
Not tested
Requires SIM card and
accepts valid E.164
numbers only
No voicemail service on
test system
Pass
Pass
Requires SIM card to
configure
Pass
Requires SIM card to
configure
Requires SIM card to
configure
Pass
Pass
Pass
8
Accessory Support
This category is related to headsets and other accessories that may be used with the
handset in conjunction with VoIP.
Supported:


Wired headsets
Mono Bluetooth headsets
Not Supported:

9
Stereo Bluetooth headsets
Configuring VoIP
The Phone Dialer on the HP iPAQ 500 series Voice Messenger can be used to make
VoIP calls in addition to normal cellular calls. VoIP can be configured to work with SIPenabled IP-PBX or other SIP servers. Refer to Section 7 above for specific
interoperability test results.
9.1 ENABLING ‘INTERNET CALLING’
Before VoIP can be configured, ‘Internet Calling’ needs to be turned on. ‘Internet
Calling’ is turned off by default. The ‘Internet Calling’ plug-in on the Home screen
displays ‘Off’ indicating that the feature is turned off. To turn the feature on, select
‘Internet Calling’ on the Home screen and press Enter. This displays the Internet Calling
Settings page. Change the ‘Use Internet Calling:’ setting from ‘Never’ to any of the other
available options. This changes the status of the plug-in on the Home screen from’Off’ to
‘Not Available’. This indicates that even though VoIP is turned on, it hasn’t been
configured yet.
9.2 CHECKING WI-FI
Wi-Fi connectivity is required for VoIP to work. Before configuring VoIP, please set-up
Wi-Fi and make sure the phone can connect to an Access Point [AP] and that Internet
Explorer Mobile can be used to browse web pages.
9.3 USING HP IPAQ SETUP ASSISTANT
Once ‘Internet Calling’ is turned on and Wi-Fi is set-up, VoIP can be configured using
the HP iPAQ Setup Assistant software included on the Companion CD. The VoIP tab
under Setup Assistant provides three categories of settings – Account, Server and
VoiceMail.
Account:
Please provide the username and password for the VoIP/SIP account. Also provide the
Domain name for the account. The username and Domain are used to construct the SIP
URI for the account as in the example below:
User name- johndoe
Domain- voipservice.sip.com
SIP URI- sip:johndoe@voipservice.sip.com
The name of the VoIP Service Provider can also be specified; this is optional.
Server:
This category is for the SIP settings associated with the SIP-enabled IP-PBX or the SIP
Server. The name/s or IP Address/es of the SIP Proxy and the SIP Registrar must be
specified here. By default, ‘Register with SIP Proxy’ is checked, indicating that the SIP
Proxy is also used as the SIP Registrar. In this case, the name or IP Address of the SIP
Proxy only needs to be provided and the same name/IP address is also used for the SIP
Registrar. If the Proxy and the Registrar are different, please uncheck ‘Register with SIP
Proxy’ and provide the name/IP address for the SIP Registrar in addition to the SIP
Proxy.
Voice Mail:
If a Voice Mail number is provided with the account, please include it here. This is
optional.
The ‘Options’ button can be used to access some advanced VoIP settings. The UDP
signaling method can be toggled between symmetric and asymmetric. Symmetric UDP
signaling is used by default. An option to enable early UDP packets on RTP and RTCP
ports is available. This enables opening of ports on a NAT allowing NAT traversal of
traffic. A prefix digit can be added to outgoing phone numbers. For example, if ‘9’ is
specified as the prefix digit, it is automatically pre-pended to all 11-digit, 10-digit and 7digit phone numbers. By default, no prefix digit is used. The DSCP field in the IP header
of voice packets contains a QoS number that determines the priority voice packets get
over data packets in the network. By default, 56 is used as the DSCP QoS number. This
can be modified to increase or decrease the priority of voice traffic.
Once all the appropriate information is provided, apply the configuration to the phone. If
Wi-Fi is on and connected to an AP, the phone will register with the specified SIPenabled IP-PBX or the SIP Server. If Wi-Fi is off, SIP registration will occur when the
next time Wi-Fi is turned on and connected to an AP. The status of the ‘Internet Calling’
plug-in will either be ‘Available’ or ‘Selected’. ‘Available’ means that the phone has
Wi-Fi access and is registered with the IP-PBX, but the next outgoing call will be over
cellular. ‘Selected’ means that the phone has Wi-Fi access, is registered with the IP-PBX
and that VoIP will be used for the next outgoing call. The Phone Dialer can be used to
make and receive VoIP calls. The Internet Calling status can be toggled between
‘Available’ and ‘Selected’ by pressing the Action [Enter] button on the Internet Calling
plug-in on the home screen.
If the status of the plug-in is ‘No Service’, it indicates that the registration was
unsuccessful. This could be due to lack of Wi-Fi access, the IP-PBX being unavailable or
some other failure.
9.4 VOIP DIAL PLAN
The dial plan for VoIP consists of dialing rules. These dialing rules are constructed using
regular expressions. Please refer to the Windows Mobile 6 documentation for information
on creating dialing rules. The dial plan is an XML file based on the OMA provisioning
standard. The Voice Messenger comes with a default dial plan which may not necessarily
work for a specific set-up. The dial plan will have to be modified and to do this, a base
XML template will be provided. This should be used to add new dialing rules specific to
the infrastructure being targeted. Once the XML template is modified to add new rules, it
should be applied to the phone/s to provision the phone/s with the updated VoIP dial
plan. This can be done using any of the provisioning methods supported by Windows
Mobile 6 –
1. OTA using OMA Client provisioning [WAP push].
2. OTA using OMA Device Management provisioning. [OMA DM server is
required].
3. Using a CAB Provisioning Format [.cpf] file which can be delivered over HTTP,
or by using a SD/MMC card or copied over to the phone directly using
ActiveSync.
4. Using Remote API [RAPI] in ActiveSync to push the provisioning XML file to
the phone.
5. Application Developers can use the DMProcessConfigXML API to provision.
Please refer to the Windows Mobile 6 documentation for additional details on the
provisioning methods listed above.
HP iPAQ Setup Assistant cannot be used to make any significant changes to the dial plan.
It can only be used to add a prefix digit to 11-digit, 10-digit and 7-digit outgoing phone
numbers. It is HIGHLY RECOMMENDED that any modifications/additions/deletions to
the dial plan should be done using any of the provisioning methods mentioned above. HP
iPAQ Setup Assistant MUST only be used to configure/modify SIP settings.
9.4.1 IMPORTANT NOTE ABOUT EMERGENCY CALLING
Emergency Calling over IP is not supported by the Voice Messenger. All emergency calls
must be placed over cellular. To ensure this, a dialing rule specifically for emergency
calling MUST be added to the VoIP dial plan. This rule will indicate what the emergency
number is and will also indicate that this number should be placed on the cellular network
only. The emergency dialing rule for the U.S is shown below:
<rule pattern='911' display='911' restrict='VoIP' />
The base template for the VoIP Dial Plan is specified below. It is HIGHLY
RECOMMENDED that the rules included in the base template should not be removed.
<wap-provisioningdoc>
<characteristic type="VoIP">
<parm name="DialPlan" value="<dialplan xmlns='http://schemas.microsoft.com/embedded/VoIP'>
<dialplan-header>
<host>#use_sipsrv_host_name#</host>
</dialplan-header>
<!-- Dial Plan rules -->
<!-- IP address rules -->
<!-- EQUIVALENT OF '\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}' -->
<rule pattern='(\d|\d\d|\d\d\d)\.(\d|\d\d|\d\d\d)\.(\d|\d\d|\d\d\d)\.(\d|\d\d|\d\d\d)' restrict='Cell,SMS' />
<!-- EQUIVALENT OF '(\d{1,3})\*(\d{1,3})\*(\d{1,3})\*(\d{1,3})' -->
<rule pattern='(\d|\d\d|\d\d\d)\*(\d|\d\d|\d\d\d)\*(\d|\d\d|\d\d\d)\*(\d|\d\d|\d\d\d)' dial='\1.\2.\3.\4'
display='\1.\2.\3.\4' restrict='Cell,SMS' />
<!—Add Emergency Dialing Rules here -->
<!—Add Other Dialing Rules here -->
<!-- SIP URI rules -->
<!-- EQUIVALENT OF '[Ss][Ii][Pp][Ss]?:\w*(\d{3})(\d{3})(\d{4})@(.+)' -->
<rule pattern='[Ss][Ii][Pp][Ss]?:\w*(\d\d\d)(\d\d\d)(\d\d\d\d)@(.+)' display='(\1) \2-\3'
restrict='Cell,SMS' />
<rule pattern='([Ss][Ii][Pp][Ss]?:)?\w*([a-zA-Z0-9_-]+)@(.+)' display='\2' restrict='Cell,SMS' />
<rule pattern='[Ss][Ii][Pp][Ss]?:\w*([^@]+)' display='\1' restrict='Cell,SMS' />
<!—Catch All -->
<rule pattern='(\d+)' dial='sip:\1@$host$' display='\1' transfer='sip:\1@$host$' />
<rule pattern='([a-zA-Z0-9_-]+)' dial='sip:\1@$host$' display='\1' transfer='sip:\1@$host$' />
</dialplan>" />
</characteristic>
</wap-provisioningdoc>
A sample dialing rule for 10-digit phone numbers is shown below. This rule pre-pends a
‘9’ to 10-digit dialed phone numbers.
<rule pattern='(\d{3})\s*(\d{3})\s*-?\s*(\d{4})(\s*[Xx]\s*\d+)?' dial='sip:9\1\2\3@$host$'
display='(\1) \2-\3'
transfer='sip:\1\2\3@$host$' />
Please refer to the Windows Mobile 6 documentation for additional details about the
VoIP Dial Plan and some examples.
9.5 ADDITIONAL CONFIGURATION
Windows Mobile 6 provides a set of registry keys to customize the WM6 SIP Client.
Some of the key customization features are provided by HP iPAQ Setup Assistant as
explained in section 9.3. The other customization options can be set by modifying the
registry. Below are some examples of the configuration options provided using the
registry –




Enable/disable redirection of SIP calls.
Allow/disallow listening for incoming SIP traffic on port 5060.
Modify the registration expiry time (default is 19 seconds).
Modify Session Timers, specifically ‘Session-Expires’ and ‘Min-SE’ (default is
90 seconds).
Please refer to the Windows Mobile 6 documentation for complete coverage of all
available configuration options and the associated registry entries.
10 Appendix A – Standards Support
10.1
SIGNALING STANDARDS IMPLEMENTED
Standard or Reference
Title/ Decription
RFC 3261
RFC 3261
RFC 2327
RFC 2246
RFC 3263
SIP: Session Initiation Protocol
Call Waiting
SDP : Session Description Protocol
TLS Protocol
Session Initiation Protocol (SIP): Locating SIP
Servers
SIP: Locating servers
DNS SRV
An Offer/Answer Model with the Session
Description Protocol (SDP)
Reliability of Provisional Responses :
Provisional Response ACKnowledgement
(PRACK)
DHCP Option for location the outbound SIP
Proxy server
Session Initiation Protocol (SIP)-Specific Event
Notification (SUBSCRIBE/NOTIFY)
A Message Summary and Message Waiting
Indication
Presence Information Data Format (PIDF)
The SIP INFO Method
Session Initiation Protocol (SIP) Extension for
Instant Messaging
Secure RTP (SRTP)
Presence Event Package for the Session
Initiation Protocol (SIP)
The Session Initiation Protocol (SIP) Refer
Method
SIP: Refer Method/ Call Transfer
Privacy Mechanism for SIP
Short term requirements for Network asserted
identity
Private extensions to SIP of asserted identify
within trusted networks
MD5
MIME content type
RTCP in SDP
Call Preferences
MD5
Diffserv
An Extension to HTTP: Digest Access
Authentication
RFC 3263 (obsoletes 2543)
RFC 2782 (obsoletes 2052)
RFC 3264
RFC 3262
RFC 3361
RFC 3265
RFC 3842
RFC 3863
RFC 2976
RFC 3428
RFC 3711
RFC 3856
RFC 3515
RFC 3515
RFC 3323
RFC 3324
RFC 3325
RFC 1321
RFC 2387
RFC 2605
RFC 3841
RFC 1321
RFC 2474
RFC 2617 (obsoletes 2069)
10.2
MEDIA/OTHER STANDARDS
Standard or Reference
Description
RFC 3550 (obsoletes RFC 1889)
RTP: A Transport Protocol for Real-Time
Applications
RFC 3551 (obsoletes RFC 1889)
RTP Profile for Audio and Video Conferences
with Minimal Control
draft-wing-behave-symmetric-rtprtcp-01.txt
RFC 2833
Symmetric RTP/RTCP ports over UDP
RTP Payload for DTMF Digits, Telephony
Tones and Telephony Signals (in-band and out
of band)
Voice codec
RTP Payload for Redundant Audio Data
G711 u/A
RFC 2198
10.3
STANDARDS NOT IMPLEMENTED
Standard or Reference
Decription
Draft-ietf-core-23
Draft-ietf-xmpp-cpim-04
RFC 3326
RFC 4028
RFC 3611
XMPP core implementation
Mapping of XMPP to CPIM
The Reason Header Fields of the SIP
Session Timers in the SIP
RTP Control Protocol Extended Reports
(RTCP XR)
(RTP) Payload for Comfort Noise (CN)
SIP Update Method
SIP Join header
SIP Call Control - Conferencing for User
Agents
SIP 'Replaces' Header
RFC 3389
RFC 3311
Draft-ietf-sip-join-xx
Draft-ietf-sipping-cc-conferencing-xx
RFC 3891
RFC 3266
RFC 3581
Call Park/Call Pickup
Support for IPv6 in Session Description
Protocol (SDP)
Symmetric Routing
G.722.1
Call Park/Call Pickup (through ‘Replaces’
header)
Extension to SIP event notification
framewirking for aggregation of notification
under the same AOR?
Internet Gateway Device (IGD) Standardized
Device Control Protocol V 1.0
RTP Payload Format for ITU-T
Recommendation G.722.1
Voice codec
G.723
Supported if a 3rd party codec is used
G.723.1
Supported if a 3rd party codec is used
RFC 3903 (Draft-ietf-sup-publish-04)
UPnP IDG
RFC 3047
iLBC
Supported if a 3rd party codec is used
G.726
Supported if a 3rd party codec is used
G.729
Supported if a 3 party codec is used
SIP Auth -AKA
AKA - Auth based on USIM
3GPP Specific RFCs/Headers
rd

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project