Avaya B5800 User Manual download pdf (Page 287)

Appendix A: Centralized deployment

example call flows

This appendix provides examples of call flows for a system that is configured in a centralized

deployment.

Routing concepts

In the example network deployment provided in this appendix, all calls that are routed within

Avaya Aura

Session Manager are converted to E.164. The primary function for this is to

support Tail-End-Hop-Off (TEHO).

E.164

E.164 is a numbering format that is recommendation by the International Telecommunications

Union - Telecommunications (ITU-T). E.164 can have a maximum of 15 digits and is preceded

by a +.

• Maximum of 15 digits (not including the preceding +).

• First part is a 1 to 3-digit country code.

• Second part is a national destination code.

• Last part is the subscriber number.

• Second and last parts are collectively known as the national number.

Tail-End-Hop-Off (TEHO)

TEHO is the process of routing a call through a private network to the closest node of the

destination call, and then routing over the public network as a local call.

Call flows

The B5800 Branch Gateway centralized solution revolves around SIP endpoints at a branch

location that registers to a Session Manager. Local trunking is provided through the B5800

Branch Gateway at the branch location. When connectivity to the Session Manager is lost, the

SIP endpoints failover and register to the B5800 Branch Gateway for connectivity.

Implementing the Avaya B5800 Branch Gateway November 2011 287

1 2 ... 282 283 284 285 286 287 288 289 290 291 292 ... 341 342

No comments

Avaya B5800 User Manual Page 287