Runtime considerations for SIP application developers
You should consider certain product runtime behaviors when you are writing Session Initiation Protocol (SIP) applications.
Container may accept non-SIP URI schemes
The SIP container will not reject a message if it doesn't recognize the scheme in the request Uniform Resource Indicator (URI) because the container cannot know which URI schemes are supported by the applications. SIP elements may support a request URI with a scheme other than sip or sips, for example, the pres: scheme has a particular meaning for presence servers, but the container does not recognize it. It is up to the application to determine whether to accept or to reject a specific scheme. SIP elements may translate non-SIP URIs using any mechanism available, resulting in SIP URIs, SIPS URIs, or other schemes, like the tel URI scheme of RFC 2806 [9].
適用於轉換使用者: When a SIP application sends a request
to a SIP URI over Transport Layer Security (TLS) in version 6.1, the
request URI scheme changes from "sip" to "sips." In the current version,
the scheme does not change. You can reverse the new behavior by changing
the application code. With a "sips" URI, the behavior remains the
same after upgrading from version 6.1 to 7.0 or later. See the information
center topic Premigration considerations for more information.trnsInvoking session listener events
SipSessionListener and SipApplicationSessionListener events are invoked only if an application requests the corresponding session object. You do this by using in your application the method shown in Table 1.| Event | Method |
|---|---|
| SipSessionListener | getSession() |
| SipApplicationSessionListener | getApplicationSession() |
參照主題