Page History

Add_workflow_for_techpubs

AUTH1 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} JIRAIDAUTH SYM-28599 REV5 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV6 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV3 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca2f03d1, userName='null'} REV1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc7d083d, userName='null'} REV2 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c8e901a1, userName='null'}

Contents:

...

Initial Configuration

I set the network configuration in the initial configuration page, but I still cannot see the SBC on the network.

...

• Calls to PSTN numbers fail. Lync declares the gateway unavailable with Event ID 46046
• Lync clients at Branch Site cannot establish MTLS connection with the Central Pool
• Lync Server 2010 Archiving Agent fails to create local queue on the SBA
• When querying Active Directory cache, attributes are missing in the search result
• Workaround for no ring back in PSTN to Lync calls

SNMP

SNMP is not a very efficient method for managing devices.  Excessive polling of the SBC Edge will have an impact on performance: CPU and memory usage increase and the number of calls per second (CPS) will drop.

When managing the SBC, you must consider a balance between the importance of calls and the management data.  If calls are more important, then you want to keep SNMP polls to a minimum and rely on SNMP traps for SBC health.  If management data is more important, just know that it will impact call performance and expect to see increased usage of the CPU and memoryPolling too frequently or polling too much data at once can lead to some undesirable behavior. Simple frequent polls (SNMP get) of one OID or one varbind is acceptable X number of seconds, and extensive polls such as SNMP walk of multiple OIDs or varbinds is acceptable X number of minutes.

Examples:

 For CPS capabilities, refer to SBC Edge Call Performance, located under SBC 1000/2000 Performance and Capacity

...

.