1. Home
    2. /
  2. Manuals
    3. /
  3. Linksys
    4. /
  4. SPA-841
    5. /
  5. 35
Page 171 / 286 Scroll up to view Page 166 - 170
Advanced Topics in SPA9000 Administration
Technology Background
SPA9000 Voice System Administration Guide
169
A
SPA400 SIP-PSTN Gateway
When a local user on the
SPA9000
network initiates a call to a PSTN subscriber, the
SPA400 acts as the SIP-PSTN gateway, which converts the SIP and RTP media
packets into the appropriate signal for transmission to the PSTN switch. For
example, if UserA calls UserD, the SIP request is routed by the SIP proxy in the
SPA9000 to the SPA400.
Figure 3
SPA400 as a SIP-PSTN Gateway
The SPA400 then converts the SIP and RTP packets it receives from UserA and
the signals it receives from the PSTN switch.
SIP Proxy
Switch
SPA9000
UserA
UserB
SPA400
1 to 4 DID lines
SIP-PSTN
Gateway
UserD
Internet (WAN) Interface
PSTN
Downloaded from
www.Manualslib.com
manuals search engine
Page 172 / 286
Advanced Topics in SPA9000 Administration
SPA9000 Architecture
SPA9000 Voice System Administration Guide
170
A
SPA9000 Architecture
This section describes the basic architecture, function, and configuration options
for the SPA9000.
Figure 4
SPA9000 Architecture
As shown, the SPA9000 provides four logical line interfaces, referred to as Line 1,
2, 3, and 4. Each line can be configured with the same or a different ITSP. Each
SPA400 also occupies one line interface. The SPA9000 has five internal clients
that register implicitly with the internal SIP proxy:
•
FXS1 (fxs1)
•
FXS2 (fxs2)
•
Call Park (callpark)
•
Auto-Attendant (aa)
•
Internal Music Server (imusic)
FXS1 and FXS2 correspond to the two physical FXS ports. The FXS ports can only
register with the local SIP proxy. The Call Park is used to maintain calls that are
parked, and AA is a scriptable auto-attendant application.
imusic
Line 1
ITSP SIP Proxy
(408)111-1000 to 7
(949)111-2000 to 7
(888)111-3000 to 7
ITSP SIP Proxy
ITSP SIP Proxy
SPA9000
aa
PSTN
SPA 400
SIP-PSTN
gateway
(408)111-1111
(408)111-1112
(408)111-1113
(408)111-1114
Line 2
Line 3
Line 4
FXS1
Application
server
Switch
FXS2
SIP Proxy
SIP Registrar
Media (RTP) Proxy
Call
park
Administration
web server
Downloaded from
www.Manualslib.com
manuals search engine
Page 173 / 286
Advanced Topics in SPA9000 Administration
SPA9000 Architecture
SPA9000 Voice System Administration Guide
171
A
Architectural Component
Function
SIP proxy and Registrar server
Accepts registration from client stations
and proxies SIP messages.
Media proxy server
Proxies RTP packets between client
stations and proxies SIP messages.
Configuration server
Serves configuration files to client stations
and auto configures un-provisioned client
stations.
Application server
Supports advanced features such as call
park/pickup, directory, directed call pickup
and group paging, hunt groups, and shared
line appearances.
Internal music source
Streams audio files to client stations (both
on-net and off-net).
The FXS1 and FXS2 can optionally be
connected to an external music source to
act as a streaming audio server (SAS).
When working in this mode, each FXS port
can handle up to 10 concurrent calls.
Administration web server
Allows configuration and monitoring of the
SPA9000
.
ATA with 2 FXS ports
Each FXS port can be connected to analog
phones, fax machine, or an external music
source. Each port can support up to two
calls simultaneously. The FXS ports can only
register to the internal proxy server.
Call park
The call park is used to maintain calls that
are parked and can handle up to 10 calls
simultaneously
Auto-Attendant
AA is a scriptable auto-attendant
application that can handle up to 10 calls
simultaneously
Downloaded from
www.Manualslib.com
manuals search engine
Page 174 / 286
Advanced Topics in SPA9000 Administration
SIP-NAT Interoperation
SPA9000 Voice System Administration Guide
172
A
SIP-NAT Interoperation
If the SPA9000 is behind the NAT device, the private IP address of the SPA9000 is
not usable for communications with the SIP entities outside the private network.
NOTE
If the ITSP offers an outbound NAT-Aware proxy, this discovers the public IP
address from the remote endpoint and eliminates the need to modify the SIP
message from the UAC.
The SPA9000 system must substitute the private IP address information with the
proper external IP address/port in the mapping chosen by the underlying NAT to
communicate with a particular public peer address/port. For this, the SPA9000
system needs to perform the following tasks:
•
Discover the NAT mappings used to communicate with the peer.
This can be done with the help of an external device, such as a STUN server. A
STUN server responds to a special NAT-Mapping-Discovery request by
sending back a message to the source IP address/port of the request, where
the message contains the source IP address/port of the original request. The
SPA9000 system can send this request when it first attempts to communicate
with a SIP entity over the Internet. It then stores the mapping discovery results
returned by the server.
•
Communicate the NAT mapping information to the external SIP entities.
If the entity is a SIP Registrar, the information should be carried in the Contact
header that overwrites the private address/port information. If the entity is
another SIP UA when establishing a call, the information should be carried in
the Contact header as well as in the SDP embedded in SIP message bodies.
The VIA header in outbound SIP requests might also need to be substituted
with the public address if the UAS relies on it to route back responses.
•
Extend the discovered NAT mappings by sending keep-alive packets.
Because the mapping is alive only for a short period, the SPA9000 system
continues to send periodic keep-alive packets through the mapping to extend
its validity as necessary.
Downloaded from
www.Manualslib.com
manuals search engine
Page 175 / 286
Advanced Topics in SPA9000 Administration
Advanced Call Control and Routing
SPA9000 Voice System Administration Guide
173
A
Advanced Call Control and Routing
•
“Configuring Vertical (Supplementary) Service Codes,” on page173
•
“Managing the Outbound Call Routing Groups,” on page175
•
“Configuring Outbound Call Codec Selection Codes,” on page177
Configuring Vertical (Supplementary) Service Codes
Users can enter vertical (supplementary) service codes, also known as star (*)
codes, to activate special calling features, such as *69 for call return. The SPA9000
Voice System is pre-configured with default star codes, but you can customize
them for your site. The codes are automatically appended to the dial plan.
STEP 1
Connect to the SPA9000 administration web server, and choose Admin access
with Advanced settings. (See
“Connecting to the SPA9000 Administration Web
Server,” on page 27
).
STEP 2
Click
Voice tab > Regional
.
STEP 3
Scroll down to the
Vertical Service Activation Codes
area or the
Vertical Service
Announcement Codes
section.
Downloaded from
www.Manualslib.com
manuals search engine

Rate

3.5 / 5 based on 2 votes.

Popular Linksys Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top