Reference13r3:Concept Softphone Redundancy

From innovaphone wiki
Jump to navigation Jump to search


Applies to

  • innovaphone devices with a PBX from version 13r3
  • innovaphone myApps (all platforms)

Configuration

The Softphone App takes the configuration that is published by the myApps client inside the connInfo object in the API model of com.innovaphone.client.

pri
The primary PBX.
sec
The secondary PBX.
phys
Explicit physical location, if configured.

See Reference13r3:Concept_myApps_Redundancy#Published_information_for_the_softphone_app for details.

Explicit physical location

Registration

In the myApps launcher

  • The softphone tries to register to the primary and the secondary PBX in an alternating manner.
  • During the registration flow, it might be redirected several times until it is registered to the PBX the user is configured on.
  • In standby cases one of the PBXes might keep the registration acting as a standby, instead of redirecting.

In the browser

The Softphone App always registers to the current PBX. As the Softphone App is loaded from the same PBX as the myApps client, the redundancy is solved by the myApps client.

Physical location

In the myApps launcher

From 13r3 SR7 the behaviour can be configured using PBX / Config / myApps / Softphone Registration / No physical location.

Note that the setting must be consistent on all PBXes in the system.

"No physical location" is off

  • If an explicit physical location is configured in the myApps client, the softphone uses it for registration.
  • Otherwise it uses the location of the primary PBX.

"No physical location" is on

  • If an explicit physical location is configured in the myApps client, the softphone uses it for registration.
  • Otherwise it uses no physical location.

In the browser

  • If an explicit physical location is configured in the URL-Parameters of the myApps client (#phys=), it is used for the registration.
  • Otherwise it uses no physical location.

Tracing

Trace flags

App
Signaling