Log Message: |
-merge work from b-client-outbound-20110213 - client outbound support (RFC 5626)
- New UserProfile settings
- clientOutboundEnabled
- setRegId
- UserProfile now tracks flow used at registration time if server indicates outbound support, and
all usages that are assigned the same UserProfile will use this flow
- ;ob parameter is added to contact headers of non-REGISTER requests if clientOutboundEnabled
- ;reg-id parameter is added to contact headers of REGISTER requests if configured
- ;+sip.instance is added to all contact headers if configured
- ClientRegistration tagContact is now static and is used in RegistrationCreator for consistency
- Keep alive pong responses are now routed from Stack to DUM Keepalive Manager
- DUM Keep alive manager will terminate flows if a pong response is not received from
an outbound enabled connection after a default of 10 seconds
-removed a bunch of non-implemented methods from DialogUsageManager.hxx
-optimized some accesses to user profile from usages
-added new makeInviteSession calls that accept an InviteSessionHandle and add an appropriate replaces header
-treat internal 503 errors the same as 408 errors when dispatching onRequestRetry callback for
ClientRegistration, ClientSubscription and ClientPublication
- allows retry logic that is consistent when using both UDP or TCP/TLS transports
- note: TCP/TLS transports get a 503 error when they cannot connect, UDP transports typically
get a 408 error when the far end is not present
-ClientRegistration changes to ensure calling requestRefresh will not assert in any state
- allow calling requestRefresh while a retry timer is running to request an immediate retry
-created onFlowTerminated callbacks on:
- ClientRegistrationHandler - default implementation is to retry registration immediately
- InviteSessionHandler - current default implementation is to do nothing
- ServerSubscriptionHandler - default implementation is to end the Subscription
- ClientSubscriptionHandler - default implementation is to reSubscribe (new Dialog)
-fix for ContactInstanceRecord equality checks - registration server was not treating contacts with the same
instance id as equal if the contact URI was different
|