Basics of NAT
NAT, Network Address Translation, is a network service that is designed to preserve the limited IP addresses in the IP-v4 scheme. It hides internal Network IP addresses of a network and exposes only one (or a few) external IP address(es) to the outside world.
Small Private IP Network comprising of KX-TDA200 PBX with TDA0480 IP-GW card and two PCs – connected to the outside Public IP Network (Example: Internet) using a NAT device. Please note that in this scenario – the only “valid” Public IP address is that of the outside interface on the NAT device 204.35.123.55. This is the only address that the outside devices “see” no matter which internal system – TDA, or PCs generates IP traffic that goes to the outside IP Cloud. Hence using NAT a company only needs a very limited set of publicly addressable IP addresses.
H.323 VoIP Packets
Difference b/w Normal Data Packets Vs H.323 Packets over IP
The main difference between a normal data packet and an H.323 VoIP packet is that a normal data packet carries its own IP address in its IP header and its source and destination port values in the TCP header. Whereas in an H.323 VoIP packet – the source IP address and source IP port is also carried in the H.323 payload body of the H.323 packet. This H.323 data payload is called Protocol Data Unit (PDU).
NAT Setup and VoIP Configurations
To understand what is involved in TDA VoIP set-up and configurations we take an example scenario consisting of two TDA sites – each connected over the IP data network via H.323 Aware NAT devices
Requirements:
NAT (a) and NAT (b) must both be H.323 Aware (i.e. NAT devices must have ability to look inside the H.323 Message Structure called Protocol Data Unit (PDU) and change Source IP address and Source Port values. Further, it should be able to properly route UDP audio packets (RTP) to internal H.323 gateways).
VoIP Configuration:
When Configuring IP-GW using MCS protocol – please make sure:
Programming at Site A• Configure IP-GW (A) at site A normally. See TDA0480 Programming Guide for details
• Configure IP-GW (B) using external IP address of NAT (b) (as if IP-GW (B) is at NAT (b)’s external IP address). This is because when Party (A) is calling Party (B) - if H.323 Call Setup message is sent from 20.0.0.3 to 192.168.1.230 – it would fail, as 192.168.1.230 is a private destination IP address. So the destination IP address has to be NAT (b)’s public IP address.
• Upload and transfer configuration and DNS files only to IP-GW (A)
Programming at Site B• Configure IP-GW (B) at site B normally. See TDA0480 Programming Guide for details
• Configure IP-GW (A) using external IP address of NAT (a) (as if IP-GW (A) is at NAT (a)’s external IP address). This is because when Party (B) is calling Party (A) - if H.323 Call Set-up message is sent from 192.168.1.230 to 20.0.0.3 – it would fail, as 20.0.0.3 is a private destination IP address. So the destination IP address has to be NAT (a)’s public IP address.
• Upload and transfer configuration and DNS files only to IP-GW (B)
NAT Configurations
When Configuring NAT (a) and NAT (b) – please make sure to:
• Configure NAT (a) to accept any H.323 packets it receives at 80.33.155.41 and then forward it internally to 20.0.0.3.
• Configure NAT (b) to accept any H.323 packets it receives at 81.35.250.170 and then forward it internally to 192.168.1.230.
Monday, July 20, 2009
Panasonic PABX TDA Series VoIP Operation Across NAT
Gold Vision Billing System
Introduction to Billing System
- Pabx Billing System is expertise software for recording and calculating telephone bills. It is integrated by latest software technologies and excellent design.
- Pabx Billing System is designed for:
Microsoft Windows NT 4.0, Service Pack 6.
Microsoft Windows Millennium, latest Service Pack.
Microsoft Windows 2000 Professional/Server, Service Pack 3 or later.
Microsoft Windows XP
Microsoft Windows 2003
- Pabx Billing Systemä requires Microsoft Office 2000 runtime (Office 9) or later to run. You also have to update all Microsoft Office 2000 Service Packs to make the VBA libraries to be more stable. If you don’t update Service Pack, there are some errors caused by the bug of Microsoft Office, which prevents the application to run smoothly.
Pabx Billing System can:
- Communicate with private exchange via serial port (RS232 standard) or IP. It is compatible with all Pabx of any manufacturer. No need to recompile or change anything to make it able to work with your Pabx.
- Online relay the calculated call data to serial printer connected to another serial port of the billing PC to print out the bill as soon as the call finishes.
- Make telephone bill, which bases not only on Extension but also on Access Code - the password used to access outside - of employee.
- Receive call detail records (CDR) directly from private exchange, then process it immediately. The real time detailed information of each call will be display on your monitor and also be saved to database.
- Output these telephone bills to Microsoft Word, Microsoft Excel, PDF Format, and HTM Format.
- Create report for core data that you have entered like department information, user information, tariff…
- Beside online receiving mode, Pabx Billing System also supports offline-receiving mode which inputs call detail records from export files of it or text files copied from private exchange.
- Require minimum resources of PCs. Pabx Billing System can run smoothly on Windows 32/64 bit and PC with low configuration. Suggested configuration for PC is Intel Pentium 800 MHz, 128 MB RAM, 300 MB Free Hard Disk or above that.
- Support Master/Slave mode. One Master billing PC is communicating directly with Pbx and many other Slave billing PCs can be used to make reports at the same time and at anywhere on your network.
- Auto-find out undeclared extensions, undeclared trunks, and already deleted extensions…
- Re-apply tariff whenever you want. Why does customer need re-applying tariff if the tariff already is in database? In fact, your telephone service provider can change the tariff, even they inform customer, but customer might forget to change tariff in database at right time. Customer can change tariff later then let Pabx Billing System re-apply the call in the pass with current tariff.
- Define call record formats during runtime. No need to obtain special version to work with your Pabx or re-compile the application.
Wednesday, February 4, 2009
Call Forwarding (FWD)/Do Not Disturb (DND) Features-1
Call Forwarding (FWD)
Description
Extensions and incoming call distribution groups can forward their calls to preset destinations. There are
several different types of forwarding, and the circumstances under which the calls are forwarded for each
type differ as follows:
Type Circumstance
All Calls Any time
Follow Me:
When an extension user fails to set this feature before leaving the
desk, this feature can be set from the destination extension.
Busy When the extension user's line is busy.
No Answer When the extension user does not answer within a preprogrammed
time.
Busy/No Answer When the extension user's line is busy or the user does not answer
within a preprogrammed time.
Conditions
[General]
• FWD for Trunk Calls/Intercom Calls
The extension user can set the FWD feature for trunk calls, for intercom calls, or for both.
• FWD from Incoming Call Distribution Group (Group FWD)
COS programming determines the incoming call distribution groups that can use this feature.
• FWD to Trunk
COS programming determines the extensions or incoming call distribution groups that can forward calls
externally.
The original extension's TRS/Barring and ARS still apply to the forwarded call.
• Trunk Call Duration
The duration of a trunk call can be restricted by a system timer. Trunk call duration is assigned
separately for calls between an extension user and an outside party, and calls between two outside
parties.
If the timer expires, the line will be disconnected. (. 1.11.8 Trunk Call Limitation)
Feature Guide
1.3 Call Forwarding (FWD)/Do Not Disturb (DND) Features
• Multiple FWD
Calls can be forwarded up to four times. The following forwarding features are counted as Multiple FWD:
– FWD—Busy or Busy/No Answer (when the destination extension is busy), or All Calls
– Idle Extension Hunting—Overflow
– Intercept Routing—Busy/DND (when the destination extension is busy or in DND mode)
– Incoming Call Distribution Group—Overflow
forwarding stops at extension E. However, forwarding can go farther in the
following cases:
– If a destination extension rings, and then the call is redirected to the forward destination by the
FWD—No Answer or Busy/No Answer feature.
– If a destination extension rings, and then the call is redirected to the intercept destination by the
Intercept Routing—No Answer feature.
– If a call waits in a queue of an incoming call distribution group, and then the call is redirected to the
overflow destination by the Queuing Time Table. (. 1.2.2.4 Queuing Feature)
In the above cases, the forwarding counter resets to zero, and the call can be forwarded up to four times
• Message Waiting
While calls are forwarded, Message Waiting information is not forwarded. The Message button light
turns on at the originally called extension. (. 1.19.1 Message Waiting)
• Idle Extension Hunting
Idle Extension Hunting applies to calls forwarded to a busy extension in an idle extension hunting group.
Feature Guide
1.3 Call Forwarding (FWD)/Do Not Disturb (DND) Features
[All Calls and Busy]
• If the forward destination is not available to answer a call, this feature is cancelled and the original
destination will ring for the following type of call:
– Doorphone call
– Trunk calls via the ELCOT, LCOT, or T1 (LCOT/GCOT) cards
[No Answer and Busy/No Answer]
• No Answer Time
The number of rings before the call is forwarded is programmable for each extension.
[Follow Me]
• This feature is only available when the original extension has disabled the "Deny Remote Operation
by Other Extension" setting on a COS basis.
Programming Manual References
PC Programming Manual
2.8.8 [2-6-1] Numbering Plan—Main—Features—FWD No Answer Timer Set
2.8.11 [2-7-1] Class of Service—COS Settings
. TRS—Call Forward to CO
. Extension Feature—Group Forward Set
. Extension Feature—Remote Operation by Other Extension
2.9.1 [3-1-1] Trunk Group—TRG Settings—Main
. CO-CO Duration Time
. Extension-CO Duration Time
2.9.10 [3-5-1] Incoming Call Distribution Group—Group Settings—Group Log / Group FWD
2.10.3 [4-1-2] Wired Extension—FWD/DND
2.10.12 [4-2-2] Portable Station—FWD / DND
PT Programming Manual
[472] Extension-to-Trunk Call Duration
[473] Trunk-to-Trunk Call Duration
[504] Call Forwarding to Trunk
[605] Call Forwarding—No Answer Time
Feature Guide References
1.1.1.6 Intercept Routing
1.2.1 Idle Extension Hunting
1.2.2.6 Overflow Feature
2.2.1 Class of Service (COS)
User Manual References
1.6.1 Forwarding Calls
Feature Guide
Incoming Call Features-4
Call Waiting
Description
Used to inform a busy extension that another incoming call is waiting. The busy extension user can answer
the second call by disconnecting the current call or placing it on hold.
The following notification method can be assigned for each extension depending on the call waiting and the
telephone type:
a) Call Waiting Tone: Tone from the handset or built-in speaker
b) OHCA: Voice from the built-in speaker
c) Whisper OHCA: Voice from the handset
d) Off: No notification.
Call Type
Notification Method
DPT Other Telephone
Intercom Call Call Waiting tone/OHCA/
Whisper OHCA/Off
Call Waiting tone/Off
Trunk Call* Call Waiting tone/Off
*: Including a doorphone call, call via an incoming call distribution group, and a trunk call transferred from
another extension.
This feature is also known as Busy Station Signalling (BSS).
Conditions
• Automatic Call Waiting
Through system programming, it is possible to select whether a call waiting tone is automatically sent
to the extension when receiving trunk calls, doorphone calls, external sensor calls and hold-recall calls.
Through system programming, it is also possible to select whether extensions will receive Automatic
Call Waiting from intercom calls.
• Call Waiting call for an extension in a VM group (DPT/DTMF) is not available.
• Data Line Security
Setting Data Line Security cancels the Call Waiting setting. (. 1.11.5 Data Line Security)
• Call Waiting Tone
A PT user can hear different Call Waiting tones for trunk call and intercom call if "Tone 2" has been
selected through personal programming (Call Waiting Tone Type Selection). If "Tone 1" has been
selected, the same Call Waiting tone will be heard for both trunk call and intercom call.
All Call Waiting tone patterns have a default (. 3.3.1 Tones/Ring Tones).
• Caller Information
With the Call Waiting tone, the caller's information flashes on the display for five seconds, followed by
a 10-second pause, then flashes again for five seconds.
• Call Waiting from the Telephone Company
Besides the Call Waiting service within the PBX, the Call Waiting tone offered by an analogue line from
the telephone company informs the extension user of another incoming trunk call that is waiting. He can
answer the second call by disconnecting the current call or placing it on hold using EFA. For details,
consult your telephone company.
Call Waiting Caller ID (Visual Caller ID):
When using the call waiting tone supplied by the telephone company over analogue lines, the waiting
Incoming Call Features-3
Intercept Routing—No Destination
Description
Provides automatic redirection of incoming trunk calls that do not have a destination assigned. The intercept
destination is an operator (tenant/PBX).
Conditions
• Intercept Routing—No Destination on/off
The Intercept Routing—No Destination feature can be enabled or disabled through system
programming.
If disabled, a reorder tone will be sent to the caller. However, the Intercept Routing—No Destination
feature always functions for calls through the ELCOT, LCOT, or T1 (LCOT/GCOT) card even when
disabled.
• If an operator (tenant/PBX) is not assigned:
The extension connected to the lowest-numbered jack will be the intercept destination.
• Intercept Routing—No Destination also applies to calls from doorphones.
Programming Manual References
PC Programming Manual
2.8.3 [2-2] Operator & BGM—PBX Operator—Day, Lunch, Break, Night
2.16.7 [10-5] Miscellaneous—Intercept—Routing to Operator - No Destination (Destination is not
programmed)
PT Programming Manual
[006] Operator Assignment
Feature Guide References
2.2.5 Operator Features
Feature Guide
1.1 Incoming Call Features
1.1.2 Internal Call Features
1.1.2.1 Internal Call Features—SUMMARY
Description
The following types of internal calls are available:
Feature Description & Reference
Intercom Call A call from one extension to another.
. 1.5.3 Intercom Call
Doorphone Call When a call from a doorphone reaches its destination, the recipient
can talk to the visitor.
. 1.17.1 Doorphone Call
[Available Destination]
The destinations of doorphone calls can be assigned for each time mode (day/lunch/break/night) (. 2.2.4
Time Service) on a doorphone port basis.
Destination
Calling from
Extension Doorphone
Wired Extension (PT/SLT/ISDN Extension/T1-OPX)
PS
Incoming Call Distribution Group
PS Ring Group
Floating Extension no. for SVM
VM Group (DTMF/DPT)
External Pager (TAFAS)
DISA
Analogue/ISDN Remote Maintenance
Idle Line Access no. + Phone no.
Trunk Group Access no. + Trunk Group no. + Phone no.
Other PBX Extension (TIE with no PBX Code)
Other PBX Extension (TIE with PBX Code)
Incoming Call Features-2
Intercept Routing
Description
Provides automatic redirection of incoming trunk and intercom calls. There are two types of Intercept
Routing as follows:
Feature Description
Intercept Routing—No Answer
(IRNA)
If a called party does not answer a call within a preprogrammed time
period (IRNA Timer), the call is redirected to the preprogrammed
destination.
Intercept Routing—Busy If a called party is already handling a call, new calls are handled as
follows:
– The call is redirected to the preprogrammed Intercept
Routing—Busy destination.
– If an Intercept Routing—Busy destination is not enabled, the
caller will hear a busy tone. However, if the call is made
through an LCOT/ELCOT or T1 [LCOT/GCOT] card, the
caller hears a ringback tone.
Intercept Routing—DND If a called party is in DND mode, the call is redirected to the
preprogrammed destination.
Intercept destinations can be assigned to extension ports.
. 2.10.1 [4-1-1] Wired Extension—Extension Settings—Option 1—Intercept Destination—When called
party does not answer—Day, Lunch, Break, Night
. 2.10.10 [4-2-1] Portable Station—Extension Settings—Main—Intercept Destination—When called party
does not answer—Day, Lunch, Break, Night
. [604] Extension Intercept Destination
When the original destination is:
The Available Intercept Destination is:
• Wired Extension (PT/SLT/T1-OPX)
The destination assigned to the original extension.
• PS
2.10.1 [4-1-1] Wired Extension—Extension Settings—
Intercept Destination
. Intercept Destination—When called party
does not answer—Day, Lunch, Break, Night
. Intercept Destination—When Called Party is
Busy
2.10.10 [4-2-1] Portable Station—Extension
Settings—Intercept Destination
. Intercept Destination—When called party
does not answer—Day, Lunch, Break, Night
. Intercept Destination—When Called Party is
Busy
. [604] Extension Intercept Destination
Feature Guide
