Linksys RTP300 User Guide - Page 64

Setting the Trunk Group Call Capacity, Inbound Call Routing for a Trunk Group, Subscriber Information

Get Linksys RTP300 - Broadband Router With 2 Phone Ports PDF manuals and user guides
UPC - 745883565658
View all Linksys RTP300 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 64 highlights

SIP Trunking and Hunt Groups on the SPA8000 Setting the Trunk Group Call Capacity The ITSP may set a limit to the number of calls that can be made on a trunk group. You can configure a trunk group's call capacity parameter to meet the requirements of the ITSP. Both incoming call and outgoing calls are counted towards this limit. The call capacity has the following impact on call handling: • Inbound calls: When the limit is reached, the Trunk UA replies 486 to the caller. • Outbound calls: When the limit is reached, the Line UA plays a fast busy tone to the caller. Note that a trunk line can make an outgoing call only through its own trunk. If that trunk reaches full capacity, it will not attempt to failover to use other trunks. You can configure this setting in the Voice tab > Trunk (T1 ... T4) page, Subscriber Information section, Call Capacity field. For more information, see "Configuring a Trunk Group," on page 67. Inbound Call Routing for a Trunk Group An incoming call is handled as follows: 1. When an incoming call is detected by the Trunk UA, the UA first checks if there is capacity to handle the call. If there is insufficient capacity, the UA rejects the call with a 486 response. 2. If there is spare call capacity, the UA consults the Contact List to determine which line or lines to ring (that is, for the proxy to send SIP INVITE to), and starts "hunting." (See "Configuring a Trunk Group," on page 67) 3. When a line is selected to ring, one or more PBX phones may be alerted, according to the PBX features and configuration. 4. The Caller ID of the external Caller is signaled by the Line UA out to the FXS port using the configured Caller ID method (FSK, DTMF, etc.). The PBX must be able to detect Caller ID signal in order for the proper Caller ID to show. 5. If the call is picked up by the PBX, the Line UA replies 200 OK with SDP to the internal Proxy. The Trunk UA in turn replies 200 OK to the ITSP and relay the Line SDP in the 200 OK message also. If all goes well, the Line UA and the ITSP equipment start exchanging RTP packets afterwards. Linksys ATA Administration Guide 64

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
Linksys ATA Administration Guide
64
SIP Trunking and Hunt Groups on the SPA8000
Setting the Trunk Group Call Capacity
The ITSP may set a limit to the number of calls that can be made on a trunk group. You can
configure a trunk group’s call capacity parameter to meet the requirements of the ITSP. Both
incoming call and outgoing calls are counted towards this limit. The call capacity has the
following impact on call handling:
•
Inbound calls: When the limit is reached, the Trunk UA replies 486 to the caller.
•
Outbound calls: When the limit is reached, the Line UA plays a fast busy tone to the
caller. Note that a trunk line can make an outgoing call only through its own trunk. If
that trunk reaches full capacity, it will not attempt to failover to use other trunks.
You can configure this setting in the
Voice tab > Trunk (T1 ... T4)
page,
Subscriber Information
section,
Call Capacity
field. For more information, see
”Configuring a Trunk Group,” on page 67
.
Inbound Call Routing for a Trunk Group
An incoming call is handled as follows:
1.
When an incoming call is detected by the Trunk UA, the UA first checks if there is capacity to
handle the call. If there is insufficient capacity, the UA rejects the call with a 486 response.
2.
If there is spare call capacity, the UA consults the Contact List to determine which line or
lines to ring (that is, for the proxy to send SIP INVITE to), and starts “hunting.” (See
”Configuring a Trunk Group,” on page 67
)
3.
When a line is selected to ring, one or more PBX phones may be alerted, according to the
PBX features and configuration.
4.
The Caller ID of the external Caller is signaled by the Line UA out to the FXS port using the
configured Caller ID method (FSK, DTMF, etc.). The PBX must be able to detect Caller ID
signal in order for the proper Caller ID to show.
5.
If the call is picked up by the PBX, the Line UA replies 200 OK with SDP to the internal Proxy.
The Trunk UA in turn replies 200 OK to the ITSP and relay the Line SDP in the 200 OK
message also. If all goes well, the Line UA and the ITSP equipment start exchanging RTP
packets afterwards.