Polycom H340 - Manual (Page 20)

20
© 2010 Polycom, Inc. All rights reserved. POLYCOM ® , the Polycom “Triangles” logo and the names and marks associated with Polycom’s products are trademarks and/or service marks of Polycom, Inc.
and are registered and/or common law marks in the United States and various other countries. All other trademarks are property of their respective owners. No portion hereof may be reproduced or
transmitted in any form or by any means for any purpose other than the recipient’s personal use without the express written permission of Polycom
Deploying SpectraLink e340, h340 and i640 Wireless Telephones BEST PRACTICES GUIDE
October 2010
4.1.3.1 Scenario One
Scenario One assumes that the handset has registered to SVP Server 1, associated to Access Point A, and
managed by SVP Server 1 (Figure 6)
 Handset communicates only to SVP Server 1 in this case
Figure 6 - Scenario One
4.1.3.2 Scenario Two
Scenario Two assumes that handset has roamed to Access Point B and is managed by SVP Server 2 (Figure 7)
 Packets to handset (from call server or PBX) are first sent through its Home SVP Server (Server 1), then
forwarded to SVP Server 2, and then transmitted by AP B to the handset
 On the return trip the handset communicates back through AP B to its “Home” SVP Server (Server 1) and
back to the call server or PBX
Figure 7 - Scenario Two
Calls between handset may bypass the call server or PBX and connect directly between SVP Alias IP addresses.
Control messaging will still go to /from the call server or PBX.
As a final note, the wireless telephone learns about all available SVP Servers IP addresses when it powers up and
does the “SRP Check-In” with the Registration SVP Server (identified in DHCP option 151 or set statically). Once the