Linksys SPA2002-ER User Guide - Page 42

VoIP Interfaces, Call Types

Page 42 highlights

- Limit the use of the gateway by PSTN Caller-ID number - Selectively forward PSTN callers to different VoIP destinations Notes: - The parameter under [Regional] tab only controls the Caller-ID signal format sent by the SPA to the Caller-ID device attached to the FXS/PHONE port; it does not apply to the caller-id signal format sent to the SPA by the PSTN switch via the FXO/LINE port. At present the SPA can only decode Bellcore FSK style Caller-ID signal sent by the PSTN switch. 4.2.3. VoIP Interfaces There are 2 VoIP interfaces in the SPA-3000. Each VoIP interface can be configured to register with a VoIP Service Provider (VSP), and to receive and make calls over the IP network. Depending on the functionality you have in mind, you can configure either or both interfaces. The VoIP1 and VoIP2 interfaces correspond to the Line 1 VoIP service, and the PSTN Line VoIP service, respectively. The [SIP] parameter group and a portion of the [Regional] parameter group apply to both VoIP interfaces. The [Line 1] and the [User 1] parameter groups are dedicated to VoIP1, while the [PSTN Line] and the [PSTN User] parameter groups to VoIP2. VoIP1 and VoIP2 interfaces can be configured independently with the same or different VSP. The same VSP account can be configured for both interfaces but the parameter must be different for each interface in this case. Most VSP require the following parameters configured on a VoIP interface: - - - - - Some VSP may also require the following parameters to be configured: - (from VSP) and = yes - and = yes 4.2.4. Call Types The type of calls supported by the SPA-3000 can be described in terms of the originating, intermediate, and terminating interfaces involved: 1. FXS to VoIP1 2. VoIP1 to FXS 3. FXO to VoIP2 4. VoIP2 to FXO 5. VoIP1 to FXO 6. FXO to VoIP2 to VoIP1 to FXS 7. FXS to VoIP1 to VoIP2 to FXO #1 and #2 are conventional VoIP calls. #3 lets a PSTN caller hop-on to use VoIP service. #4 lets a VoIP caller hop-off to use PSTN service. #5 is similar to #4 except the caller establishes the VoIP call leg by calling the VoIP1 interface instead of the VoIP2 interface. #6 allows the PSTN call to ring the FXS port phone; we called this "ringing thru". #7 allows you to call the PSTN from the phone. Notes: © 2003 - 2004 Sipura Technology, Inc Proprietary (See Copyright Notice on Page 2) 42

  • 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

© 2003 - 2004 Sipura Technology, Inc
Proprietary (See Copyright Notice on Page 2)
42
-
Limit the use of the gateway by PSTN Caller-ID number
-
Selectively forward PSTN callers to different VoIP destinations
Notes:
-
The <Caller-ID Method> parameter under [Regional] tab only controls the Caller-ID signal format
sent by the SPA to the Caller-ID device attached to the FXS/PHONE port; it does not apply to the
caller-id signal format sent to the SPA by the PSTN switch via the FXO/LINE port. At present the
SPA can only decode Bellcore FSK style Caller-ID signal sent by the PSTN switch.
4.2.3.
VoIP Interfaces
There are 2 VoIP interfaces in the SPA-3000. Each VoIP interface can be configured to register with
a VoIP Service Provider (VSP), and to receive and make calls over the IP network. Depending on the
functionality you have in mind, you can configure either or both interfaces. The VoIP1 and VoIP2
interfaces correspond to the Line 1 VoIP service, and the PSTN Line VoIP service, respectively.
The [SIP] parameter group and a portion of the [Regional] parameter group apply to both VoIP
interfaces. The [Line 1] and the [User 1] parameter groups are dedicated to VoIP1, while the [PSTN
Line] and the [PSTN User] parameter groups to VoIP2.
VoIP1 and VoIP2 interfaces can be configured independently with the same or different VSP. The
same VSP account can be configured for both interfaces but the <SIP Port> parameter must be
different for each interface in this case.
Most VSP require the following parameters configured on a VoIP interface:
-
<Proxy>
-
<User ID>
-
<Password>
-
<Register>
-
<Register Expires>
Some VSP may also require the following parameters to be configured:
-
<Outbound Proxy> (from VSP) and <Use Outbound Proxy> = yes
-
<Auth ID> and <Use Auth ID> = yes
4.2.4.
Call Types
The type of calls supported by the SPA-3000 can be described in terms of the originating,
intermediate, and terminating interfaces involved:
1. FXS to VoIP1
2. VoIP1 to FXS
3. FXO to VoIP2
4. VoIP2 to FXO
5. VoIP1 to FXO
6.
FXO to VoIP2 to VoIP1 to FXS
7.
FXS to VoIP1 to VoIP2 to FXO
#1 and #2 are conventional VoIP calls. #3 lets a PSTN caller hop-on to use VoIP service. #4 lets a
VoIP caller hop-off to use PSTN service. #5 is similar to #4 except the caller establishes the VoIP call
leg by calling the VoIP1 interface instead of the VoIP2 interface. #6 allows the PSTN call to ring the
FXS port phone; we called this “ringing thru”. #7 allows you to call the PSTN from the phone.
Notes: