Linksys SPA2002-ER User Guide - Page 52

Line 1 VoIP Fallback to PSTN, VoIP-To-PSTN Calls Via VoIP1 Interface Call Type #5

Page 52 highlights

xxxxxxx xxxxxxx User dials 8 to start Outside Dial Tone. When user dials a 7-digit number, SPA prepends it with 1408 and routes the call to pstn.sipura.com:5061, with user-id = joe, and pwd = bell_pwd, and NAT mapping enabled User dials 8 to start Outside Dial Tone. When user dials a 7-digit number, SPA prepends it with 1408 and routes the call to Gateway 2, but to port 5061 with user-id = "Alex Bell", pwd = bell_pwd, and NAT mapping disabled With the call-routing capability, one can use the same phone to make outbound calls to Line 1 VoIP or the PSTN line attached to the FXO port. In fact, the SPA can bridge a 3-way conference with one VoIP leg and one PSTN call leg. One can also setup multiple PSTN gateways at different locations and configured Line 1 to use different gateway when dialing certain numbers. Notes: - gw0 - gw4 identifiers can only be used in [Line 1]. They are not allowed in [PSTN Line], n = 1 to 8 - The "usr", "pwd", and "nat" parameters, on the other hand, are allowed in all dial plans - The PSTN gateway will apply the to further limit the calls that can be made by the Line 1 caller to the PSTN; this dial plan may be set to "none". In general calls routed from Line 1 to the PSTN are processed by 2 dial plans. - The SPA does not support call transferring the VoIP peer to the PSTN peer, or vice versa, in a 3way call or 3-way conference that involves one VoIP call leg and one PSTN call leg. 4.9. Line 1 VoIP Fallback to PSTN When power is removed from the SPA-3000, the FXS port will be connected to the FXO port. In this case, the telephone attached to the FXS port is electrically connected to the PSTN service via the FXO port. When power is applied to the SPA, the FXS port will be disconnected from the FXO port. However, if the PSTN line is in use when the power is applied to the SPA, the relay will not be flipped until the PSTN line is released. This is done so that the SPA will not interrupt any call in progress on the PSTN line. When Line 1 VoIP service is down (due to registration failure or loss of Ethernet link), SPA can be configured to automatically route all outbound calls to the internal gateway if ([Line 1] tab) is set to "yes". The PSTN gateway applies the to further limit the calls that can be made by the Line 1 caller during the fallback operation; this dial plan may be set to "none". This case also belongs to call type #7 and the voice path is (1)Æ(2)Æ(4)Æ(6)Æ(7). 4.10. VoIP-To-PSTN Calls Via VoIP1 Interface (Call Type #5) All PSTN gateway calls can be routed from the VoIP2 interface if the user can dedicated one VoIP account for the PSTN Line. Line 1 and the PSTN Line can also be configured with the same VoIP account if they use different . If the service provider allows multiple REGISTER contacts and simultaneous ringing, both VoIP interfaces can register periodically with the service provider. In this case, both VoIP interfaces will receive inbound calls to this shared account. The PSTN Line should be configured with a sufficiently long before the call is automatically answered to provide PSTN gateway function. If the service provider does not allow more than one REGISTER contacts, then the PSTN Line should not register. In this case, only Line 1 will ring on the inbound call to this VoIP account (since it is the only line registered with the service provider). Line 1 can have the call "forwarded" to the PSTN line after a configurable delay using the Call-Forward-On-No-Answer feature with "gw0" as the forward © 2003 - 2004 Sipura Technology, Inc Proprietary (See Copyright Notice on Page 2) 52

  • 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)
52
<8,:1408>xxxxxxx<:@pstn.sipura.com:5
061;usr=joe;pwd=joe_pwd;nat>
User dials 8 to start Outside Dial Tone. When user dials
a 7-digit number, SPA prepends it with 1408 and routes
the call to pstn.sipura.com:5061, with user-id = joe, and
pwd = bell_pwd, and NAT mapping enabled
<8,:1408>xxxxxxx<:@gw2:5061;usr=”Al
ex Bell”;pwd=”anything”;nat=no>
User dials 8 to start Outside Dial Tone. When user dials
a 7-digit number, SPA prepends it with 1408 and routes
the call to Gateway 2, but to port 5061 with user-id =
“Alex Bell”, pwd = bell_pwd, and NAT mapping disabled
With the call-routing capability, one can use the same phone to make outbound calls to Line 1 VoIP
or the PSTN line attached to the FXO port. In fact, the SPA can bridge a 3-way conference with one
VoIP leg and one PSTN call leg. One can also setup multiple PSTN gateways at different locations
and configured Line 1 to use different gateway when dialing certain numbers.
Notes:
-
gw0 – gw4 identifiers can only be used in [Line 1]<Dial Plan>. They are not allowed in [PSTN
Line]<Dial Plan
n
>,
n
= 1 to 8
-
The “usr”, “pwd”, and “nat” parameters, on the other hand, are allowed in all dial plans
-
The PSTN gateway will apply the <Line 1 VoIP Caller DP> to further limit the calls that can be
made by the Line 1 caller to the PSTN; this dial plan may be set to “none”. In general calls routed
from Line 1 to the PSTN are processed by 2 dial plans.
-
The SPA does not support call transferring the VoIP peer to the PSTN peer, or vice versa, in a 3-
way call or 3-way conference that involves one VoIP call leg and one PSTN call leg.
4.9. Line 1 VoIP Fallback to PSTN
When power is removed from the SPA-3000, the FXS port will be connected to the FXO port. In this
case, the telephone attached to the FXS port is electrically connected to the PSTN service via the
FXO port. When power is applied to the SPA, the FXS port will be disconnected from the FXO port.
However, if the PSTN line is in use when the power is applied to the SPA, the relay will not be flipped
until the PSTN line is released.
This is done so that the SPA will not interrupt any call in progress on
the PSTN line.
When Line 1 VoIP service is down (due to registration failure or loss of Ethernet link), SPA can be
configured to automatically route all outbound calls to the internal gateway if <Auto PSTN Fallback>
([Line 1] tab) is set to “yes”. The PSTN gateway applies the <Line 1 Fallback DP> to further limit the
calls that can be made by the Line 1 caller during the fallback operation; this dial plan may be set to
“none”. This case also belongs to call type #7 and the voice path is (1)
(2)
(4)
(6)
(7).
4.10.
VoIP-To-PSTN Calls Via VoIP1 Interface (Call Type #5)
All PSTN gateway calls can be routed from the VoIP2 interface if the user can dedicated one VoIP
account for the PSTN Line. Line 1 and the PSTN Line can also be configured with the same VoIP
account if they use different <SIP Port>. If the service provider allows multiple REGISTER contacts
and simultaneous ringing, both VoIP interfaces can register periodically with the service provider. In
this case, both VoIP interfaces will receive inbound calls to this shared account. The PSTN Line
should be configured with a sufficiently long <VoIP Answer Delay> before the call is automatically
answered to provide PSTN gateway function.
If the service provider does not allow more than one REGISTER contacts, then the PSTN Line should
not register. In this case, only Line 1 will ring on the inbound call to this VoIP account (since it is the
only line registered with the service provider). Line 1 can have the call “forwarded” to the PSTN line
after a configurable delay using the Call-Forward-On-No-Answer feature with “gw0” as the forward