Collapse AllExpand All

18.2.9.4. Scenarios within a Network with SPE activated Nodes and SPE deactivated Nodes Previous topic Parent topic Child topic Next topic

HOME and VISITED: SPE deactivated and TRADITIONAL/SPEcapable

HOME:
  • SPE deactivated
  • phones: TRADITIONAL/SPEcapable
VISITED:
  • SPE deactivated
  • phones: TRADITIONAL/SPEcapable
spe_mhfa_02-2.jpg

HOME: SPE deactivated and TRADITIONAL/SPEcapable, VISITED: SPE activated and TRADITIONAL/SPEcapable and SECURE/CIPHER

HOME:
  • SPE deactivated
  • phones: TRADITIONAL/SPEcapable
VISITED:
  • SPE activated
  • phones: TRADITIONAL/SPEcapable and SECURE/CIPHER
spe_mhfa_03-2.jpg

HOME: SPE activated and TRADITIONAL/SPEcapable and SECURE/CIPHER, VISITED: SPE activated and TRADITIONAL and SPEcapable and SECURE/CIPHER

HOME:
  • SPE activated
  • phones: TRADITIONAL/SPEcapable and SECURE/CIPHER
VISITED:
  • SPE activated
  • phones: TRADITIONAL and SPEcapable and SECURE/CIPHER
spe_mhfa_04-2.jpg
one-2.jpg
A TRADITIONAL client (without SPE support) is never accepted as a VISITED station for a SECURE or CIPHER client. Call processing on the VISITED switch is aware of this and rejects the remote login attempt with "Remote Login not possible" (before asking the user to enter his/her PIN).

HOME: SPE activated and TRADITIONAL/SPEcapable and SECURE/CIPHER, VISITED: SPE activated and TRADITIONAL and SPEcapable

HOME:
  • SPE activated
  • phones: TRADITIONAL/SPEcapable and SECURE/CIPHER
VISITED:
  • SPE activated
  • phones: TRADITIONAL and SPEcapable
spe_mhfa_05-2.jpg
one-2.jpg
A TRADITIONAL client (without SPE support) is never accepted as a VISITED station for a SECURE or CIPHER client. Call processing on the VISITED switch is aware of this and rejects the remote login attempt with "Remote Login not possible" (before asking the user to enter his/her PIN).