Pointspan 5.2 Features and Enhancements

Transcription

Proprietary and Contents Section
ii
Aastra – 2808-001
1st Edition (February 9, 2009)
© Copyright 2009 Aastra. All rights reserved.
Information in this manual may change with product revisions. Aastra may add features
or enhancements to the product(s) and/or program(s) described in this manual at any
time.
Technical Publications freezes the information in this manual based on the specified
software and hardware releases. Publications writers incorporate such changes into newly
released publication editions. Publications writers will incorporate any modifications
provided to them after the publication release date into the next scheduled release of
the publication.
Aastra Intecom furnishes the application described in this manual under a license
agreement and customers may use or copy information in the manuals only in accordance
with the terms of the agreement.
Contact Information
Address any reader comments to:
Aastra
Customer Information Group Manager, M/S 1N
2811 Internet Boulevard
Frisco, TX 75034-1851
You may also send email to [email protected]
What to Expect when Contacting Company
Technical Publications will email responses to customers within seven business days of
the contact. Note that product support is not available through this email address. For
product support, contact the Aastra Customer Service Center (CSC) at 1-800-729-1872.
Aastra may use or distribute review comments and information without incurring
obligation.
Trademarks and Acknowledgements
Product registered trademarks and copyrights of the products included in this publication
include Pointspan®, Centergy®, Centergy Remote®, and Centergy Reporting®, as
registered trademarks of Aastra.
This publication identifies all other products or services mentioned herein by the
trademarks, service marks, or product names designated by the companies that market
those products. The companies producing these trademarks and registered trademarks
control ownership of them. Make all inquiries concerning such trademarks directly to
those companies.
Aastra - 2808-001
iii
Revision History
The following represents the revision history of this publication:
iv
Revision
Number
Date
Completed
2808-001
02/09/2009
Point of Contact
Description
Aastra Technical
Publications – Bev
Marsh
Initial release of this
publication.
Aastra – 2808-001
Table of Contents
1st Edition (February 9, 2009) ....................................................................................iii
Contact Information ....................................................................................................iii
What to Expect when Contacting Company ...............................................................iii
Trademarks and Acknowledgements ..........................................................................iii
Revision History.......................................................................................................... iv
About This Publication ........................................................................................................... 1
Overview ...................................................................................................................... 1
Audience....................................................................................................................... 1
Organization ................................................................................................................. 1
Reference Publications ................................................................................................. 2
Terms and Acronyms ................................................................................................... 3
Chapter 1 Aastra SIP Phone Station Features .................................................................... 1
Aastra SIP Phone SPN ACD Features ................................................................................ 2
Agent Statistics............................................................................................................. 2
Queue Depth................................................................................................................. 3
Aastra SIP Phone Preferred Line ........................................................................................ 3
Preferred Line Behavior by Phone Feature .................................................................. 3
Busy Lamp Field/Direct Station Select............................................................................... 4
Functionality................................................................................................................. 4
Example ................................................................................................................. 4
Directed Call Pickup of BLF Line (DSS)..................................................................... 4
BLF Key....................................................................................................................... 5
Assign a BLF Key ........................................................................................................ 5
BTNS – Add a BLF Key .............................................................................................. 6
FONE Command.......................................................................................................... 8
3x-type Phones Renamed.................................................................................................. 10
Aastra - 2808-001
v
5x-type Phones Renamed.................................................................................................. 10
Expansion Modules........................................................................................................... 10
New Button Template Types...................................................................................... 10
Key Type ............................................................................................................. 10
Button Template Types........................................................................................ 10
Features Supported on the Expansion Module Keys.................................................. 11
Model 536M............................................................................................................... 11
Model 560M............................................................................................................... 13
Column Display Format....................................................................................... 14
Using the 560M .......................................................................................................... 14
CLASS Services Remote Access for SIP Stations and Trunks ........................................ 15
SPAR Command ........................................................................................................ 15
Auto Dial for the 9143i, 9480i, and 9480i CT .................................................................. 16
Multi-Ring ........................................................................................................................ 16
Chapter 2 SPN Integrated Trunk Gateway via SIP.......................................................... 17
Overview........................................................................................................................... 17
Functionality ..................................................................................................................... 17
SIP Registration.......................................................................................................... 17
Security....................................................................................................................... 17
SIP Authentication............................................................................................... 17
Transport Layer Security (TLS) .......................................................................... 17
SIP Stations ................................................................................................................ 17
SIP Trunks ........................................................................................................................ 18
Connectivity......................................................................................................... 18
Inbound Calls.................................................................................................................... 18
Dialing and Routing ................................................................................................... 18
En-bloc Signaling ................................................................................................ 18
Inbound Trunk Group Selection................................................................................. 18
Inbound Trunk Selection ............................................................................................ 19
vi
Aastra – 2808-001
Trunk Glare ................................................................................................................ 19
No Inbound Trunk Available ..................................................................................... 20
Digit Analysis and Routing ........................................................................................ 20
Dialed and Direct Inward Dial (DID) .................................................................. 20
Terminated ........................................................................................................... 21
ACD Calls .................................................................................................................. 21
Outbound Calls ................................................................................................................. 21
Routing ....................................................................................................................... 21
Routing Calls to Local SIP Trunks............................................................................. 21
Short Term Queuing................................................................................................... 21
Outpulsed Number ..................................................................................................... 21
SIP Gateway Trunk Group Selection ......................................................................... 22
Remote Trunk Unavailable ........................................................................................ 22
Outbound Call Failures .............................................................................................. 23
Trunk Glare ................................................................................................................ 23
Pass-through Dialing......................................................................................................... 23
Class of Service Restrictions...................................................................................... 24
Data ............................................................................................................................ 24
Call Detail Recording (CDR) ..................................................................................... 24
Configuration .................................................................................................................... 25
Configure the AudioCodes Gateway.......................................................................... 25
Configure Pointspan ................................................................................................... 25
Licensed SIP Trunks and SIP Destinations ................................................................ 25
Define the System Wide Domain Name in SPAR ..................................................... 25
Create the SIP Trunk Group to Route Calls to the PSTN Gateway ........................... 27
SIP Trunk Group Parameter Descriptions ........................................................... 27
Define the PSTN Gateway in the new SIPG Command ............................................ 30
Parameter Descriptions ........................................................................................ 30
Build the SIP Trunk Card and Allocate SIP Trunk Ports ........................................... 35
Aastra - 2808-001
vii
CFG/SGW............................................................................................................ 36
UGRP/FDD.......................................................................................................... 37
UGRP/NPA.......................................................................................................... 37
ROUT Command................................................................................................. 38
PDT Command .................................................................................................... 38
PointSpan Utilities ............................................................................................................ 38
PointSpan Alarm ........................................................................................................ 38
CFG > SGW ............................................................................................................... 39
TUTL Display ............................................................................................................ 40
Chapter 3 911 Enhancements.............................................................................................. 41
Chapter 4 LLDP-MED ........................................................................................................ 43
LLDP-MED Support for Aastra SIP Stations ................................................................... 43
LLDP-MED Processing ............................................................................................. 43
LLDP-MED VLAN Auto-Discovery ......................................................................... 44
Administrative Advantages.................................................................................. 44
Emergency Location Identification Number (ELIN) ................................................. 44
Transmission of ELIN by SIP Station ................................................................. 44
Processing of ELIN.............................................................................................. 44
LLPD-MED Configuration ........................................................................................ 45
Aastra SIP Station Configuration File Parameters............................................... 45
FONE Command for LLDP-MED ............................................................................. 46
Emergency Location Identification by IP Address ........................................................... 48
Enable ELIP for a SIP Station.................................................................................... 48
Manage Emergency Location Identifiers for IP addresses......................................... 48
Define an Emergency Location Identifier for an IP address range...................... 48
Delete Emergency Location Identifier for an IP Address Range......................... 49
Modify Emergency Location Identifier for IP Address Range............................ 49
Display Emergency Location Identifiers for IP Address Range.......................... 49
Emergency Location Identifier Determined by IP Address Operation ...................... 50
viii
Aastra – 2808-001
Process an Emergency Call.................................................................................. 50
Determine the IP Address of a SIP Station.......................................................... 50
Prioritization Methods that Determine the Emergency Calling Party Number ... 50
Restrictions .......................................................................................................... 51
#*9 Diagnostic to speak Emergency Location Identifier Number ............................. 51
Chapter 5 IPMI Tool............................................................................................................ 53
Intelligent Platform Management Interface (IPMI) .......................................................... 53
IPMI Commands on the ECS ..................................................................................... 53
Chapter 6 SNMP Traps ....................................................................................................... 55
SNMP Traps from PointSpan ECS ................................................................................... 55
Requirements.............................................................................................................. 55
SNMP Trap Message Format and Content................................................................. 55
Man/Machine SNMP Parameters ............................................................................... 58
Console Monitor SNMP Command ........................................................................... 60
Console Messages ...................................................................................................... 60
Chapter 7 Sip Registration CIM, Event, EAC Update ARC............................................ 63
OAI CIM, Event, and ARC Messages .............................................................................. 63
Configuration ............................................................................................................. 63
Functionality............................................................................................................... 63
SIP Registration CIM........................................................................................... 63
Update Emergency Calling Party Number ARC ................................................. 64
OAI Requirements...................................................................................................... 64
CIM Message Formats ............................................................................................... 64
For Registration from SIP Stations:..................................................................... 64
For Registration from SIP Trunks: ...................................................................... 65
For Registration from SIP Gateways: .................................................................. 65
ARC Message Format for Update Emergency CPN .................................................. 66
SIP Registration Information ID ................................................................................ 67
SIP Gateway ID.......................................................................................................... 68
Aastra - 2808-001
ix
Chapter 8 Pointspan Alarms ............................................................................................... 69
SIP Alarms for SPN.......................................................................................................... 69
0359............................................................................................................................ 69
3700............................................................................................................................ 70
3703............................................................................................................................ 73
3704............................................................................................................................ 75
3705............................................................................................................................ 76
3706............................................................................................................................ 77
3710............................................................................................................................ 78
3720............................................................................................................................ 79
3730............................................................................................................................ 81
3790............................................................................................................................ 81
Modified Alarms............................................................................................................... 82
3600............................................................................................................................ 82
x
Aastra – 2808-001
About This Publication
Overview
This publication provides information on new features and enhancements provided by
Pointspan switch software, version 5.2.
Audience
This publication provides information for all users of Pointspan switches that run or will
run version 5.2 software.
Organization
This publication contains the following chapters.
Aastra - 2808-001
Chapter, Topic
Description
Chapter 1, Aastra SIP Phone Station Features
Describes new station features.
Chapter 2, SPN Integrated Trunk Gateway via
SIP
The initial release of SPN trunking
supports basic trunk calls using SIP
signaling to a VoIP SIP media gateway
that converts the SIP trunks to digital
(ISDN PRI, T1) or analog trunks that
interconnect to the Central Office (CO).
The AudioCodes Mediant 1000 is used as
the gateway.
Chapter 3, 911 Enhancements
Pointspan 5.2 introduces enhancements to
emergency calling.
Chapter 4, LLDP-MED
The Aastra IP phones support Link Layer
Discovery Protocol for Media Endpoint
Devices (LLDP-MED).
Chapter 5, IPMI Tool
The IPMI tool resides on the SPN server
and is used by the ECS server to remotely
reboot, power-on, and query the status of
the SPN server (power on or off).
Chapter 6, SNMP Traps
Simple Network Management Protocol
(SNMP) is an internet-standard protocol
for managing devices on IP networks. The
SNMP protocol specifies ways that a
SNMP manager can monitor and control
an SNMP agent.
1
Chapter, Topic
Description
Chapter 7, Sip Registration CIM, Event, EAC
Update ARC
Pointspan 5.2 introduces new OAI
messages that provide notification when a
SPN SIP device registers with the
Pointspan system.
Chapter 8, Pointspan Alarms
New and modified alarms for Pointspan
5.2.
Reference Publications
The following publications provide related information. All are new for Pointspan 5.2.
2
Publication Number
Title
Description
2754-nnn
SPN Installation and
Operations
Provides the SPN installation
procedures.
2755-nnn
SPN Database
Man/Machine Commands for
SPN. New procedures for
creating SIP IP phones for
SPN. Procedures and
commands for maintenance and
support of SIP phones.
2735-nnn
6753i IP Phone User Guide
for SPN
Information and Procedures for
the 6753i IP phone on the SPN.
2736-nnn
for SPN
2737-nnn
for SPN
2738-nnn
6757i CT IP Phone User
Guide for SPN
the 6757i CT IP phone on the
SPN.
2741-nnn
33i (9143i) IP Phone User
Guide for SPN
2742-nnn
35i (9480i) IP Phone User
Guide for SPN
2743-nnn
35i CT (9480i CT) IP Phone
User Guide for SPN
SPN.
2756-nnn
for SPN
2757-nnn
480i CT IP Phone User
Guide for SPN
SPN.
Aastra – 2808-001
Publication Number
Title
Description
2758-nnn
for SPN
5015-nnn
Pointspan Alarms Online
Help V5.0.
Updated with new alarms for
SPN and various other changes.
2822-nnn
SoftACDAgent Toolbar
Installation and configuration
information for the toolbar.
Terms and Acronyms
The following terms apply to related information contained in this publication.
Aastra - 2808-001
Term
Definition
AIP
Alarm Information Processing.
ALI
Automatic Location Identification.
ASN
Abstract Syntax Notation.
BER
Basic Encoding Rules.
BLF
Busy Lamp Field.
CM
Console Monitor.
CP
Call Processing.
CPN
Calling Party Number.
DLS
Directory Lookup Service on the Pointspan System.
DSS
Direct Station Select.
EAC
Emergency Associated Calling Party Number. (FONE
Command).
ECS
Pointspan Enterprise Control Server.
ELIN
Emergency Location Identification Number.
ELIP
Emergency Location Identification Determined by IP Address.
IANA
Internet Assigned Numbers Authority.
IP
Internet Protocol (IP) is a data-oriented protocol used for
communicating data across a packet-switched network.
IP Address
An identifier for a computer or device on a TCP/IP network.
Networks using the TCP/IP protocol route messages based on
the IP address of the destination. The format of an IP address
is a 32-bit numeric address written as four numbers separated
by periods. Each number can be zero to 255.
3
4
Term
Definition
IPMI
Intelligent Platform Management Interface - The IPMI tool
resides on the SPN server and is used by the ECS server to
remotely reboot, power-on, and query the status of the SPN
server (power on or off)
IPN
Internet Protocol Node
LLDP-MED
Link Layer Discovery Protocol – Media Endpoint Discovery.
 Auto-discovery of LAN policies (such as VLAN) leading
to "plug and play" networking.

Device location discovery to allow creation of location
databases and, in the case of VoIP, E911 services.

Extended and automated power management of Power
over Ethernet endpoints.

Inventory management, allowing network administrators
to track their network devices, and determine their
characteristics (manufacturer, software and hardware
versions, serial / asset number).
MAC Address
Media Access Control address. It is a number that acts like a
name for each phone. It is located on the white sticker on the
bottom of the phone.
MIB
Management Information Base.
PDU
Protocol Data Unit.
PSAP
Pointspan Application Processor.
SIP – Session Initiation
Protocol
The protocol for VoIP and other text and multimedia sessions,
like instant messaging, video, online games and other services.
SNMP
Simple Network Management Protocol.
SPN
SIP Pointspan Node - Provides integrated SIP and Pointspan
station and system features.
Aastra – 2808-001
Aastra - 2808-001
TDM
Time-Division Multiplexing (TDM) - A type of digital
multiplexing where two or more signals or bit streams are
transferred apparently simultaneously as sub-channels in one
communication channel, but physically are taking turns on the
channel.
VLAN
Virtual Local Area Network. A VLAN is a logical local area
network (or LAN) that extends beyond a single traditional
LAN to a group of LAN segments, given specific
configurations.
VoIP – Voice Over IP
Voice over Internet Protocol (VoIP) is a technology that
allows you to make telephone calls using a broadband Internet
connection instead of a regular (or analog) phone line.
5
6
Aastra – 2808-001
Chapter 1
Aastra SIP Phone Station Features
The following new station features are available on the SPN for Aastra SIP phones in
Pointspan 5.2.
Feature
Description
Station Features
SIP Phone ACD

Agent Statistics.

Queue Depth.
SoftACDAgent Toolbar
Provides ACD and other SIP phone features to softphone
users.
SIP Phone Preferred Line
Returns the LCD display back to the preferred line after a
call ends (incoming or outgoing).
SIP Phone/ITE Phone
Busy Lamp Field
Busy Lamp Field (BLF) provides:
SIP Phone Expansion
Modules
Aastra - 2808-001
Two new ACD feature keys for agent SIP phones:

Status display of a voice line configured on another
station.

Directed Call Pickup of the ringing BLF line.

The ability to place a call to the monitored BLF line
using the BLF key.
Two expansion modules are available for the 6755i, 6757i,
and 6757i CT phones. (Maximum of 1 expansion module
per phone.)

536M - 18 keys in each column (totaling 36 keys).

560M - 20 keys available on each page (totaling 60
softkeys)
CLASS Services Remote
Access for SPN SIP
Phones
The CLASS Services Remote Access feature allows a
remote user (a SIP Station or user connecting to Pointspan
via a SIP Trunk) to setup Call Forward-All, CLASS
Selective Call Forward, and CLASS Anonymous Call
Rejection features for a directory number (that supports
those CLASS services) on Pointspan.
3x-type Phones Renamed
Aastra 33i, 35i, and 35i CT phones are renamed.
Auto-Dial
Auto Dial for the 9143i, 9480i, and 9480i CT.
Multi-Ring
In Pointspan 5.2.F, SIP Trunks can be used to access the
remote destination.
1
Aastra SIP Phone SPN ACD Features
Two ACD feature keys have been added to the button template:

Agent Statistics

Queue Depth
Agent Statistics
The Agent Statistics feature enables the agent to display current individual agent statistics
on the LCD display of the Aastra SIP phones.
The following statistics display when the Agent Statistics softkey is pressed:
Screen Display
2
Description
Agent Name and Extension
Agent name and extension
Online Dur
Online Duration
AVL
Available
The percentage of time available to
receive calls
ACD
Automatic Call
Distribution
Percentage of time answering ACD
calls
WRP
Wrap-up
Percentage of time in Wrap-up state
HLD
Hold
Percentage of time in Hold state
WRK
Work
Percentage of time in Work state
INC
Incoming
Percentage of time on incoming
calls
OUT
Outgoing
Percentage of time on outgoing calls
INT
Internal
Percentage of time on internal calls
Total ACD calls
Total number of ACD calls
Avg ACD Dur
Average duration of ACD calls
#OUTG
Outgoing
Total number of outgoing calls
#INCM
Incoming
Total number of incoming calls
Aastra – 2808-001
Queue Depth
The Queue Depth feature enables SIP agent phones to display current queue information
on the LCD display.
The following information displays with the Queue Depth softkey is pressed:
Acronym Displayed
Description
CIQ
Number of Calls In Queue
AOL
Number of Agents Online.
Aastra SIP Phone Preferred Line
The Preferred Line feature returns the LCD display back to the preferred line after a call
ends (incoming or outgoing). The next time the phone goes off-hook, it selects the
preferred line.
The number of seconds it takes for the phone to switch back to the preferred line is
determined by the Preferred Timeout parameter in the aastra.cfg configuration file.
There are no Man/Machine requirements for this feature. L1 will always be the preferred
line.
Preferred Line Behavior by Phone Feature
The following table provides the behavior of the preferred line focus feature with other
features on the phone.
Aastra - 2808-001
Phone Feature
Preferred Line Behavior
speeddial
The line is already specified when the speeddial is created. The
phone switches back immediately after the call ends.
conference
For incoming calls, the phone switches back immediately after the
call ends.
transfer
For incoming or outgoing calls, the current behavior is that the same
line used to transfer the call does not change. For incoming calls, the
phone switches back immediately after the call transfers.
blf
The phone switches back immediately after the call ends.
park
voicemail
redial
dialing
For incomplete dialing on a non-preferred line, the focus does not
change if some digits are entered. If no digits are entered or digits
were cleared, the focus changes to the preferred line after the timeout has passed without activity on the phone.
3
Phone Feature
Preferred Line Behavior
caller id
Always displays.
factory default
Factory default and recovery mode clears the "preferred line" and
"preferred line timeout" parameters, and the phone operates in a nonpreferred line mode.
Busy Lamp Field/Direct Station Select
The Busy Lamp Field (BLF)/Direct Station Select (DSS) feature allows display of the
status of a voice line configured on another station. The total number of BLF/DSS keys
configured on all stations in the system cannot exceed 5000. A maximum of 50 BLF keys
can be configured per station.
Functionality

The BLF-monitored line on a SIP station can monitor any station in the system (ITE,
STE, SIP, etc.)

Ring-Splash Option - The phone can be configured to play a ring-splash tone when a
call is placed to a BLF-monitored line.
Example
A manager has a BLF line configured on his phone for monitoring the status of a
worker’s phone use. Three indicators show the status of the worker’s monitored line:
Icon
Display
Description
LED Status on your phone
BLF-monitored line is active.
Solid
BLF-monitored line is idle.
Off
BLF monitored line is ringing.
Blinking
Directed Call Pickup of BLF Line (DSS)

4
The BLF monitoring station can pick up a ringing call on a BLF line. The user:
–
Hears the Ring-Splash and/or sees the LED blinking with the bell icon displayed.
–
Presses the BLF key.
–
Picks up the handset or presses the speaker key and is connected with the party
that called the BLF line.
Aastra – 2808-001

The BLF monitoring station must NOT be in a call pickup group to use Directed Call
Pickup.
If the line associated with the BLF key is in a call pickup group; then when the BLF is
called and the user presses the BLF key to answer the call, they may pick up another
ringing line in the call pickup group instead of the BLF line.
BLF Key
A call can be placed to BLF directory number by pressing BLF key:

The BLF key acts as speed dial key when the BLF-monitored line is idle.

The call is originated on the registered line associated with the BLF key.
Assign a BLF Key
Three steps are required to assign a BLF key:
1. Define the key labeling format and the DLS name format in the SPAR command.
2. Assign the BLF key(s) in the BTNS command.
3. Assign the voice line to the BLF key in the FONE command.
New SPAR Parameters
Description
BLL BLF Key labeling format
This parameter defines the format that will be used for the
LCD label display for BLF keys on SIP stations with
softkeys and the 560M expansion module. The key can be
labeled with the name or number of the line being
monitored by the BLF key. The LCD display for a BLF
key has 8 characters available to display a name.
The name can be displayed in two different formats:
1) Six characters of the first name with last initial, or
2) First initial with six characters of the last name
Example:
George Washington can be displayed as “G Washin” or
“George W”
The display name is read from the DLS database. In order
to display the first initial and last name, call processing
needs to know how the name is stored in DLS. A new
SPAR parameter, DNF is used to provide this information
to CP.
Example:
SELECT COMMAND => SPAR
SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES => U
ENTER UPDATE TYPE or ?......................P => U
Aastra - 2808-001
5
New SPAR Parameters
Description
SPECIFY SYSTEM PARAMETER TO MODIFY or - or ?. => BLL
BLF KEY LABEL FORMAT: D, F, L or ? .........F
BLF KEY LABEL FORMAT
D...USE DIRECTORY NUMBER
F...USE FIRST NAME AND LAST INITIAL FROM DLS
L...USE FIRST INITIAL AND LAST NAME FROM DLS
BLF KEY LABEL FORMAT: D, F, OR L ...........F => F
*** VERIFY/DISPLAY ***
** UPDATABLE SYSTEM PARAMETERS
08/27/08
16:35:10


BLL...SIP BLF KEY LABEL FORMAT...........FIRST NAME + LAST INITIAL


RETURN CONTINUES DISPLAY..... =>
DOES UPDATE VERIFY ? =>
DNF DLS Name Format
This parameter provides information to call processing about
how the DLS name is stored. This parameter indicates whether
the name is stored as:

First name first - George Washington or

Last name first - Washington, George
SPECIFY SYSTEM PARAMETER TO MODIFY or - or ?. => DNF
DLS DIRECTORY NAME FORMAT: F, L, or ?.......F => ?
DLS DIRECTORY NAME FORMAT
F = DLS NAME FORMAT: FIRSTNAME LASTNAME
L = DLS NAME FORMAT: LASTNAME, FIRSTNAME
DLS DIRECTORY NAME FORMAT: F, L, or ?.......F =>
SPECIFY SYSTEM PARAMETER TO MODIFY or - or ?. =>
08/27/08
16:35:10


DNF...DLS DIRECTORY NAME FORMAT..........FIRSTNAME LISTED FIRST
BTNS – Add a BLF Key
New BTNS Parameter
Description
BSLF
Assign a Busy Lamp Field key - (ITE, STE, SIP, etc).
Example:
SELECT COMMAND => BTNS
SELECT MODE: PRINT, DISPLAY, UPDATE, SEARCH, TITLES => U
SELECT MODE: C-Create; M-Modify or D-Delete.. => M
SPECIFY TEMPLATE NUMBER:..................... => 157
6
Aastra – 2808-001
New BTNS Parameter
Description
Specify BTNS Field to Modify or - or ?....... => EKY
EXTENSION KEY NUMBER TO MODIFY: Return=END.. => 5
EKY-5
TYPE: U=Unas; Lx; Feature or ?...UNAS => ?
AAAN..Agent Auto Answer
ASTS..ACD Agent Statistics Dsp
BSLF..Busy Lamp Field
CLLR..Callers
DIR1..Directory - Internal
DIR3..Directory - Contacts
DNDB..Do Not Disturb
MAIL..Voice Mail
OAI1..OAI Feature 1
OAI3..OAI Feature 3
OAI5..OAI Feature 5
OAI7..OAI Feature 7
OFFL..Agent Sign-on
PKUP..Call Pickup
RSSS..News Services
WRAP..Agent Work/Wrap
AGUN..Agent Unavailable
AUTD..Automatic Dial
CFWD..Call Forward
CREC..Call Record
DIR2..Directory – Corporate
DIR4..Directory – Combined
EMPT..Empty
MSGD..Message Desk
OAI2..OAI Feature 2
OAI4..OAI Feature 4
OAI6..OAI Feature 6
OAI8..OAI Feature 8
PARK..Call Park
QUEU..ACD - Queue Depth
SPD1..Speed Dial
EKY-5
TYPE: U=Unas; Lx; Feature or ?...UNAS => BSLF
EXTENSION KEY NUMBER TO MODIFY: Return=END.. =>
Specify BTNS Field to Modify or - or ?....... =>
57i with 560 expansion
** BUTTON TEMPLATE # 157
TYPE: SIP / 57LE
**
** LINE/CALL APPEARANCE ASSOCIATIONS
L1.....SELECT
L2.....CALL APPEARANCE..L1
L3.....SELECT
L5.....UNASSIGNED
L6.....UNASSIGNED
L7.....UNASSIGNED
L8.....UNASSIGNED
L9.....UNASSIGNED
**
********* KEY ASSIGNMENTS *********
KEY
L1.....SELECT
KEY
KEY
L3.....SELECT
KEY
TKEY...1.....FEATURE..........Callers
TKEY...2.....FEATURE..........Voice Mail
TKEY...3.....UNASSIGNED
TKEY...4.....FEATURE..........Forward
TKEY..10.....UNASSIGNED
SKEY...1.....FEATURE..........Queue Depth
SKEY...2.....UNASSIGNED
SKEY...4.....FEATURE..........Call Pkup
SKEY...6.....FEATURE..........Call Park
SKEY...7.....FEATURE..........On/Offline
SKEY...8.....FEATURE..........Wrap/Work
SKEY..10.....FEATURE..........Msg Desk
Aastra - 2808-001
08/20/08
13:00:13
7
New BTNS Parameter
Description
SKEY..11.....FEATURE..........AutoAnswer
SKEY..12.....FEATURE..........CallRecord
SKEY..13.....FEATURE..........Un-avail
SKEY..14.....UNASSIGNED
SKEY..17.....FEATURE..........OAI 1
EKEY...1.....FEATURE..........Busy Lamp
EKEY...4.....FEATURE..........Agent Stat
EKEY...6.....UNASSIGNED
EKEY..59.....UNASSIGNED
EKEY..60.....UNASSIGNED
RDL...REDIAL KEY.........................ENABLE
CNF...CONFERENCE KEY.....................ENABLE
XFR...TRANSFER KEY.......................ENABLE
DOES UPDATE VERIFY ? => Y
FONE Command
EKY/EKEY keys are expansion modules keys.
New FONE Parameters
Description
BLF Assignments
Assign a BLF line to a BLF key.
SELECT COMMAND => FONE
SELECT MODE: PRINT, DISPLAY, UPDATE => U
UPDT MODE: C-Create M-Modify D-Delete........ => M
ENTER PORT, LOCATION, WORK AT HOME or ?...... => 2.2.1.10
PORT TYPE....................SIP
Specify Field to Modify or - or ?............ => BLF
BLF ASSIGNMENTS (Button #-Type-Number):
EKY01-BLF -4002
EKY02-BLF -2001
EKY03-BLF -4006
EKY05-BLF
BLF BUTTON NUMBER: or ? Return=END........... => ?
Enter BLF button number as follows
SKYxx for softkey xx
TKYxx for top softkey xx
PKYxx for programmable key xx
EKYxx for expansion key xx
BLF BUTTON NUMBER: or ? Return=END...........
VOICE LINE DIRECTORY NUMBER or ?.............
USER GROUP...................................
ASSOCIATED SIP LINE NUMBER...................
BLF ASSIGNMENTS (Button #-Type-Number):
EKY01-BLF -4002
EKY02-BLF -2001
EKEY - New key
types for the
expansion modules
=>
=>
=>
=>
EKY05
2005
1
1
EKY03-BLF -4006
EKY05-BLF -2005
BLF BUTTON NUMBER: or ? Return=END........... =>
8
Aastra – 2808-001
New FONE Parameters
Description
Specify Field to Modify or - or ?............ =>
VERIFY DISPLAY FORMAT: N, D, or ?...........D =>
*** VERIFY DISPLAY ***
***...STATION......................PORT: 002.2.01.10
***...STATION EQUIPMENT TYPE.............SIP
***...<mac>.CFG FILE VERSION.............On File=08/20/08 13:00:22
In Use=08/20/08 12:51:15
SPT...SIP PHONE TYPE.....................AASTRA 57I w/560M
BTP...BUTTON TEMPLATE NUMBER.............157


KEY
TYPE
LINE ASSIGNMENT
L1.........LINE SELECT....DRN:4010
-UGP:1...RING
HFA – INACTIVE
L2.........CALL APPEAR....DRN:4010
-UGP:1...RING
HFA – INACTIVE
L3.........LINE SELECT....DRN:4011
-UGP:1...RING
HFA – INACTIVE
L4.........CALL APPEAR....DRN:4011
-UGP:1...RING
HFA – INACTIVE
TOP KEY #
TYPE
FEATURE ID
1........FEATURE........Callers
2........FEATURE........Voice Mail
3........FEATURE........UNASSIGNED
4........FEATURE........Call Forward
SOFT KEY # TYPE
FEATURE ID
1........FEATURE........ACD - Queue Depth
4........FEATURE........Call Pickup
6........FEATURE........Call Park
7........FEATURE........Agent Sign-on
8........FEATURE........Agent Work/Wrap
10........FEATURE........Message Desk
11........FEATURE........Agent Auto Answer
12........FEATURE........Call Record
13........FEATURE........Agent Unavailable
17........FEATURE........OAI Feature 1
EXPN KEY # TYPE
FEATURE ID
1........FEATURE........Busy Lamp Field
4........FEATURE........ACD Agent Statistics Dsp
AGENT
AGENT
Mail-MSG DISP
Mail-MSG DISP
4002/1
2001/1
4006/1
(L1)
(L1)
(L3)
2005/1
(L1)


Aastra - 2808-001
9
New FONE Parameters
Description
Three Aastra SIP Phones have been renamed:
Old
New
Aastra 33i
Aastra 9143i
Aastra 35i
Aastra 9480i
Aastra 35i CT
Aastra 9480i CT
Old
New
Aastra 53i
Aastra 6753i
Aastra 55i
Aastra 6755i
Aastra 57i
Aastra 6757i
Aastra 57i CT
Aastra 6757i CT
Expansion Modules
Two expansion modules are available for the 6755i, 6757i, and 6757i CT phones
(maximum of 1 expansion module per phone).

536M - 18 keys in each column (totaling 36 keys).

560M - 20 keys available on each page (totaling 60 softkeys)
New Button Template Types
Key Type
The new key type in the button template is “EKEY/EKY”.
Button Template Types
New button templates types for the expansion modules are:
10
Type
Phone
55SE
AASTRA 6755I 536M
55LE
AASTRA 6755I 560M
Aastra – 2808-001
Type
Phone
57SE
AASTRA 6757I 536M
57LE.
AASTRA 6757I 560M
7CSE
AASTRA 6757I CT 536M
7CLE
AASTRA 6757I CT 560M
Features Supported on the Expansion Module Keys
Expansion Module keys support the same features as the phone keys.
Feature
Feature
AAN
Agent Auto Answer
AGUN
Agent Unavailable
ASTS
ACD Agent Statistics Dsp
AUTD
Automatic Dial
BSLF
Busy Lamp Field
CFWD
Call Forward
CLLR
Callers
CREC
Call Record
DIR1
Directory - Internal
DIR2
Directory – Corporate
DIR3
Directory - Contacts
DIR4
Directory – Combined
DNDB
Do Not Disturb
EMPT
Empty
MAIL
Voice Mail
MSGD
Message Desk
OAI1
OAI Feature 1
OAI2
OAI Feature 2
OAI3
OAI Feature 3
OAI4
OAI Feature 4
OAI5
OAI Feature 5
OAI6
OAI Feature 6
OAI7
OAI Feature 7
OAI8
OAI Feature 8
OFFL
Agent Sign-on
PARK
Call Park
PKUP
Call Pickup
QUEU
ACD - Queue Depth
RSSS
News Services
SPD1
Speed Dial
WRAP
Agent Work/Wrap
Model 536M
The 536M provides 18 keys in each column (totaling 36 keys) on the keypad. Each key
has an LED for call status indication. Paper labels are provided for key labeling.
Aastra - 2808-001
11
Figure 1. Model 536M Expansion Module
Figure 2. Model 536M Keys
12
Aastra – 2808-001
Figure 3. 55i with 536M Expansion Module (Max 1 per phone)
Model 560M
The 560M provides:

An LCD screen for displaying key labels.

3 keys at the bottom left of the unit that represent "Page 1", "Page 2", and "Page 3" of
the LCD display.

10 keys in each column providing 20 softkeys available on each page (totaling 60
softkeys per 560M.)

Each key has an LED to indicate call status.
Figure 4. Model 560M Expansion Module
Aastra - 2808-001
13
Column Display Format
The 560M Expansion Module screen displays softkeys in column format. The function
keys on the bottom left of the Module allow you to display 3 full screens of keys. Each
screen consists of 2 columns.
Using the 560M
Step
1.
Action

Result
Press the top key for Page 1.
Or

Press the middle key for Page 2.
Or

2.
Press the bottom key for Page 3.
Press the desired feature key.
Figure 5. 560M Page 1 Screen
14
Aastra – 2808-001
Figure 6. 6757i CT with 560M Expansion Module (Max 1 per phone)
CLASS Services Remote Access for SIP Stations and Trunks
The CLASS Services Remote Access feature allows a remote user (SIP Station or user
connecting to Pointspan via a SIP Trunk) to set up three specific CLASS Service features
for a directory number that supports these CLASS service features on Pointspan. No
other CLASS services are implemented. This means that a SIP Station can remotely
access CLASS features for other types of stations but cannot access them itself.
The following 3 CLASS features are available for SIP stations and trunks.
CLASS Feature
Turn ON
Turn OFF
Call Forward-All
*72
*73
Selective Call Forward
*63 for Access
Anonymous Call Rejection
*77 ON
*87 OFF
SPAR Command
As a part of the feature, the CIG field in the SPAR command for an SPN partition must
be set to the CLASS Services IVC Group to be used for both SIP Stations and SIP Trunks
when changing either the Selective Call Forward or Anonymous Call Rejection features.
This IVC Group is not needed if only the Call Forward-All feature is to be changed
remotely; however, without the IVC prompt, the user could easily be confused.
Aastra - 2808-001
15
Auto Dial for the 9143i, 9480i, and 9480i CT
The Auto Dial feature is now available for the 9143i (33i), the 9480i (35i), and the 9480i
CT (35i CT) phones.
Multi-Ring
Multi-Ring is a PointSpan feature that allows additional external destinations to be
alerted at the same time the internal station rings. The station or the Multi-Ring
destination that answers first receives the call. An example of this capability is to ring a
user’s cell phone at the same time their voice line rings on their station. One or more
Multi-Ring facilities can be assigned to one voice line.
In Pointspan 5.2.F and above, SIP Trunks can be used to access the remote destination.
See 276002 Pointspan 5.0 Features and Enhancements.
16
Aastra – 2808-001
Chapter 2
SPN Integrated Trunk Gateway via SIP
Overview
The initial release of SPN trunking supports basic trunk calls using SIP signaling to a
VoIP SIP media gateway that converts the SIP trunks to digital (ISDN PRI, T1) or analog
trunks that interconnect to the Central Office (CO). The AudioCodes Mediant 1000 and
AudioCodes MP-114 FXS_FXO are used as the gateway(s).
Functionality
SIP Registration
The following SIP Registration options are supported:

Implicit Registration - The SIP gateway does not explicitly register with Pointspan.
Instead, Pointspan database identifies the location of the SIP gateway and Pointspan
performs an internal, implicit registration.

Explicit SIP Registration per Gateway - A SIP gateway initiates a single explicit SIP
Registration to indicate the gateway and all gateway trunks are available.
All SIP trunks associated with a SIP gateway are placed Maintenance Out-of-Service
(MOS) until an explicit or implicit registration of the SIP gateway completes
successfully. At that time, the affected trunks are idled and placed in the appropriate SIP
trunk group.
Security
SIP Authentication
All SIP REGISTER and INVITE messages received to place a call on a SIP trunk are
authenticated using the SIP Digest method of authentication.
Transport Layer Security (TLS)
Transport Layer Security (TLS) is not supported.
SIP Stations
A SIP gateway can support one or more SIP stations attached to that gateway. The SIP
gateway would normally pass along the SIP signaling and RTP packets to Pointspan,
allowing Pointspan to control the SIP station. However, if the network between
PointSpan and AudioCodes fails, the SIP gateway can then take control to allow the
stations to communicate locally and/or route to local SIP trunks also attached to the
gateway.
Aastra - 2808-001
17
Chapter 2, SPN Integrated Trunk Gateway via SIP
SIP stations are optionally assignable to a SIP gateway. A SIP station attached to a SIP
gateway registers and places and receives calls like any standalone SIP station. However,
the SIP station configuration maintained and generated by Pointspan is affected by the
use of the gateway in the path between the SPN and the station.
Pointspan configures a SIP station attached to a SIP Gateway as follows:

Outbound proxy - Set to the IP address of the SIP Gateway instead of the SPN.

Proxy - Set to the IP address of the Session Border Controller (SBC) if an SBC exists
between the SPN and the SIP Gateway. This causes the SIP Gateway to forward the
SIP messages sent by the station to the Session Border Controller, which forwards
them to the SPN.
Aside from the difference in SIP station configuration, a SIP station behind a SIP
Gateway operates the same as a standalone SIP station.
SIP Trunks
Connectivity
SIP trunks are able to call or be the destination of a call from any type of station (SIP,
ITE, STE), an attendant, or any type of trunk (SIP, ISDN PRI, T1, IXL, analog).
Connections between a SIP trunk and any non-IP device require an IPI circuit within the
connection path to provide IP to TDM conversion. Connections between a SIP trunk and
any IP device (another SIP trunk or a SIP station) within the same partition or between
partitions interconnected using the same IP network does not require the use of an IPI
circuit. However, connections between a SIP trunk and any IP device in a different
partition that is NOT interconnected using the same IP network requires two IPI circuits,
and potentially one or more RSP links, in the connection.
Inbound Calls
Dialing and Routing
En-bloc Signaling
For an incoming SIP trunk call, only en-bloc signaling is supported. The entire
destination number, and any authorization code and/or account code, is received in the
SIP INVITE message. Existing domestic ISDN PRI trunks also only support en-bloc
signaling.
Inbound Trunk Group Selection
Since an inbound SIP trunk call is received from the SIP gateway instead of from a
specific SIP trunk, a method must be used to identify the specific SIP trunk group from
which a SIP trunk is obtained to process the inbound call.
If a SIP Inbound Call - Destination Selection Table exists for a SIP Gateway, the table is
searched for an entry with matching originating and/or destination SIP URIs:

18
If a matching entry exists in the table, the entry indicates one of the following:
Aastra – 2808-001
–
Identifies the SIP trunk group to use for the call. In addition, the entry identifies
the actual destination number digits, the destination number plan and type, and
inter-LATA carrier code to use for the call. This allows prefix digits to only be
used to select the trunk group for the incoming call; these prefix digits can then
be removed from the destination number used to place the call. If removed, the
prefix digits do not appear in CDR and are otherwise not used by Pointspan.
–
Indicates the call is blocked.

If the table does not have a defined entry matching the received information in the
INVITE, a default entry in the table is used.

Otherwise, no SIP Inbound Call - Destination Selection Table is assigned to the SIP
Gateway. All inbound calls are blocked as described below.
If the trunk group selection process yields no match in the Destination Selection Table
(including when no Destination Selection Table exists):

The call is terminated with a SIP " 404 Not Found" response.

An aborted call CDR record using the new code "Call Restricted-SIP Trunk Call with
No Matching Destination Selection" is generated.

No trunk group or logical trunk port is identified in the aborted call CDR record.

No alarm is generated on Pointspan.
If the trunk group selection process yields an indication to block the call:

The call is terminated with a SIP “403 Forbidden” response.

An aborted call CDR record using a new code ("System Access Denied-SIP Blocked
Call-Destination Selection" or "System Access Denied-SIP Blocked Call-Calling
Party Selection") is generated.

No trunk group or logical trunk port is identified in the aborted call CDR record.

No alarm is generated on Pointspan.
Otherwise, the selection process must yield a SIP trunk group from which a trunk is
obtained to use for the call. In addition, the selection process yields the destination
number, the destination number plan and type, and inter-LATA carrier code.
Inbound Trunk Selection
A SIP trunk assigned to the appropriate gateway is obtained from the selected SIP trunk
group. A SIP trunk group may contain trunks from multiple SIP gateways, so the trunk
obtained must be assigned to the SIP gateway from which the INVITE was received.
Trunk Glare
If no SIP trunk assigned to the gateway is available in the trunk group and the trunk
group chooses to NOT IGNORE glare, a check is made for any pending outbound SIP
trunk call to that SIP gateway using a trunk from that trunk group. An outbound SIP
trunk call is considered pending when an INVITE has been sent but not response message
has yet been received.
Aastra - 2808-001
19
If one or more pending outbound SIP trunk calls exist, the last pending call is considered
as experiencing trunk glare. Pointspan cancels the SIP INVITE request, releasing the
existing trunk for use by the inbound call. The outbound call restarts route guide
processing to select another trunk for that call.
No Inbound Trunk Available
If no SIP trunk is available after attempting to resolve trunk glare, the inbound call is
terminated with a SIP “503 Service Unavailable” response. An aborted call CDR record
using the new "Call Blocked-No SIP Trunk Available" code is generated; no logical
trunk port will be identified in the CDR record. No alarm is generated on Pointspan.
However, the All Trunks Busy (ATB) count is incremented within the inbound trunk
group, regardless as to whether the trunk group has any available trunks belonging to
other SIP gateways.
Digit Analysis and Routing
The inbound SIP Trunk Group determines how the dialed digits are to be interpreted and
routed:
Dialed and Direct Inward Dial (DID)
Dialed number or DID directory number obtained from the destination number,
destination number plan and type, and inter-LATA carrier code, in the same manner as
processed for an inbound ISDN PRI trunk call.
The dialed digits may consist of some or all of the following:

Prefix digit(s) selecting the dial plan to use
–
SIP Trunk Group optionally specifies a Pre-defined Dialing Level (PDL) to use
in place of receiving these digits.

Prefix or postfix authorization code

Prefix or postfix account code

Destination number
The call is routed using:
20

Normal Routing - Dialed digits are processed, translated, and routed using the User
Group settings and tables.

DNIS Routing - The User Group DNIS Routing table is searched for the dialed
number. If a match is found, the call routes to the directory number specified by the
DNIS Routing entry.

Both DNIS Routing and Normal Routing - If the dialed number exists in the DNIS
Routing table, the call routes to the DNIS Routing directory number; otherwise, the
dialed digits are processed, translated, and routed using the User Group settings and
tables.
Aastra – 2808-001
Terminated
The call terminates on one of the following, as selected by the inbound SIP Trunk Group:

Attendant

Directory Number specified by SIP Trunk Group
ACD Calls
SIP trunk calls arriving at an ACD pilot are immediately answered and become billable,
while non-SIP trunk calls are not billable while in queue unless an announcement is
played.
Outbound Calls
Routing
The existing User Group tables controlling the selection of a Route Guide to use for an
outbound call are used. The selected Route Guide then chooses the trunk groups used for
the outbound call. As with other types of trunk groups, an available (idle) trunk is
selected from a SIP Trunk Group. That trunk is used for the call.
Routing Calls to Local SIP Trunks
It is often desirable and sometimes required to route calls to a public trunk local to the
call originator. For example, emergency 911 calls must be delivered to a trunk near the
location of the caller.
In order to route a call to a SIP trunk that is local to the call originator, the existing
Pointspan Physical Partitioning Feature is used. Physical Partitioning allows groups of
users in separate physical locations to be assigned separate User Groups (maximum 1000
User Groups). Each User Group supports unique call routing tables while optionally
sharing Call Handling Parameters with other User Groups. The User Group call routing
tables must then be setup to select Route Guides that choose SIP Trunk Groups local to
that caller.
Short Term Queuing
When no trunks are available and the Route Guide selects short-term queuing, the call
waits for a trunk to become available in trunk groups specified in the route guide,
including SIP Trunk Groups. A call can simultaneously short term queue on SIP Trunk
Groups and other types of trunk groups.
Outpulsed Number
Only en-bloc signaling is supported; the entire destination number is sent in the SIP
INVITE message. The Prefix Digit Table (PDT) determines the string of destination
number digits, the destination number plan and type, and the destination Inter-LATA
Carrier Code. The PDT is processed in the same manner as a call to an ISDN PRI trunk,
Aastra - 2808-001
21
except that operator selection causes the appropriate digits to be outpulsed similar to a
destination T1 or analog trunk.
The destination number defined by the PDT is sent in both the Request-URI and “To:”
URI of the sent SIP INVITE message.
SIP Gateway Trunk Group Selection
The SIP Gateway definition within Pointspan optionally specifies an Outbound Call Destination Number Translation Table. If the table exists, call processing locates an entry
in the table matching the outbound SIP Trunk Group and outpulsed number, number plan
and number type. That entry specifies the contents of the destination number sent in the
SIP INVITE to the SIP gateway. The translation table may identify prefix digits used by
the SIP gateway to determine what outbound trunk group (on the gateway) to which the
call must be routed.
The prefix digits are only used to select the trunk group within the SIP Gateway. They
are not considered part of the destination number. Therefore, they will not appear in CDR
and are not otherwise used by Pointspan.
If the Outbound Call - Destination Number Translation Table does not exist, only the
destination number built using the PDT is sent. The destination number is sent in a “sip:”
URI as the URI User Name, with no leading “+” character. The domain name (or domain
IP address) is that of the SIP Gateway. If the PDT identified an inter-LATA carrier code,
that carrier code is included in a Carrier Id Code (";cic=") in the “sip:” URI. No other
URI fields (display name or phone-context) is sent.
As an alternative to providing prefix digits in the Outbound Call - Destination Number
Translation Table, prefix digits may be added to the destination number in the PDT.
However, these prefix digits will be considered as part of the destination number and thus
will appear in CDR.
Remote Trunk Unavailable
When a call is placed out a SIP trunk, if the received response code is within a specific
set of ”remote trunk unavailable” response codes, the response code indicates the SIP
gateway could not continue to route the call because a remote trunk is unavailable. This
may occur when the SIP gateway has one or more trunks to the Central Office out-ofservice.
Pointspan takes the following actions:

The SIP Trunk Group from which the SIP trunk was obtained is removed from the
Route Guide used by the outbound call.

The outbound call restarts routing at the beginning of the Route Guide, without the
SIP Trunk Group.

The existing SIP trunk is idled to be made available for other calls.
This processing allows more SIP trunks to be available to the gateway than
corresponding trunks on the gateway to the Central Office. When this occurs, the SIP
Trunk Group is removed from the Route Guide used to obtain another trunk, therefore:
22
Aastra – 2808-001

Calls cannot obtain and use trunks from any other SIP gateway that may be available
in the removed outbound trunk group.

Calls cannot short-term queue within Pointspan on the trunks within that SIP Trunk
Group. However, if available, short-term queuing may take place within the SIP
gateway.
Outbound Call Failures
When a call is placed out a SIP trunk, if no response is received to the SIP INVITE or the
received response code is within a specific set of “failure” response codes, a SIP trunk
failure has occurred. This indicates the SIP gateway is not responding, or has an internal
failure. Alarm TRNK-3001 is generated when the failure occurs and another trunk is
selected for the outbound call.
A trunk signaling failure count is incremented for each failure and cleared whenever the
trunk successfully is used. Once the trunk failure threshold is exceeded, alarm TRNK3006 is generated and the SIP trunk is placed Maintenance Out-of-Service (MOS).
If a SIP gateway fails (before the gateway service check detects the failure), many
TRNK-3001 and TRNK-3006 alarms may be generated before taking all of the SIP
trunks related to the gateway out-of-service. However, this operation is consistent with
the current handling of other types of trunks and should be familiar to operations
personnel.
Trunk Glare
In addition to the previously discussed trunk glare processing related to handling of an
inbound SIP trunk call, when a call is placed out a SIP trunk and the received response
code is within a specific set of “trunk glare” response codes, the call is considered as
experiencing trunk glare. This case of glare occurs when the SIP gateway responds to the
outbound trunk call from Pointspan BEFORE sending a SIP INVITE for the inbound
trunk call.
Pointspan takes the following actions:

The outbound call restarts routing at the beginning of the Route Guide.

The existing outbound SIP trunk is idled to be made available for other calls,
including any subsequently received inbound call. Note that the outbound SIP trunk
is idled after the outbound call restarts route guide processing so that the trunk is not
available for the outbound call.
Trunk glare normally will only be an issue when this is the last trunk available in a trunk
group defined at a specific SIP gateway, and the SIP gateway is in the process of
selecting that trunk.
Pass-through Dialing
For outbound calls, pass-through dialing of digits dialed by a call originator is supported.
The call originator may be any type of station (SIP, ITE, STE), an attendant, or trunk
(SIP, ISDN PRI, T1, IXL, analog). The only exception is that connectivity between SIP
trunks and DPN trunks is NOT supported (SIP trunks are not capable of calling or being
called by DPN trunks).
Aastra - 2808-001
23
Originating SIP Stations and SIP Trunks send pass-through digits as DTMF events within the RTP stream, according to RFC 2833, “RTP Payload for DTMF Digits, Telephony
Tones and Telephony Signals”. These pass-through digits pass directly to a destination
SIP Station or SIP Trunk within the RTP stream. Pointspan does not monitor or have
access to these digits; therefore, they cannot be recorded in CDR or disabled.
Non-SIP originators (such as ITEs, STEs, attendants, analog trunks, etc.) connect to a
destination SIP Trunk utilizing an IPI circuit to convert the TDM voice to RTP packets.
Pass-through dialed digits dialed by the non-SIP originator are either actual DTMF tones
sent by the originator or are converted to a DTMF tone by Pointspan. Upon detecting a
received DTMF tone from the originator, the IPI generates a corresponding DTMF event
RTP packet, according to RFC 2833. That packet is sent in the RTP stream to the SIP
Trunk.
Similarly, originating SIP Stations and SIP Trunks connect to a non-SIP destination using
an IPI. Pass-through digits sent by the originator are received as DTMF event RTP
packets by the IPI, which then generates the appropriate DTMF tone that is sent to the
destination.
Since pass-through digits dialed by a SIP Station or SIP Trunk are contained with-in the
RTP stream, they cannot be disabled or recorded in CDR.
Class of Service Restrictions
Existing Class of Service restrictions related to trunks applies to SIP trunks. This
includes dialing restrictions, time-of-day restrictions, and feature restrictions.
Data
Only transmission of Voice and Modem/FAX is supported. No transmission of data is
supported.
Call Detail Recording (CDR)
Recording of calls using a SIP trunk is the same as that for other types of trunks. SIP
trunks are identified using the SIP Trunk Group number and SIP trunk logical port
number.
In some instances, a trunk group or trunk logical port number is not available. If an
inbound call is blocked at the point a trunk group is selected, no trunk group is available.
If a trunk cannot be obtained from a trunk group for an inbound call, no trunk logical port
number is available. In these cases, the CDR record is identified with the new SIP
Gateway Abort call type.
The SIP Gateway is ONLY identified in SIP Gateway Abort CDR records. For calls
identifying a SIP trunk, the SIP Gateway can be determined from the specific logical
trunk port number.
24
Aastra – 2808-001
Configuration
Configure the AudioCodes Gateway
The AudioCodes gateway is configured separately by Aastra installation personnel.
Configure Pointspan
Configure the following PointSpan tables to build a SIP trunk to a PSTN gateway:
1. Call the Aastra CSC to activate the number of licenses purchased for SIP Trunks.
1. Define the System Wide Domain Name in SPAR.
2. Use the Man/Maching PSWD command to enable the new SIPG command.
3. Create the SIP trunk group that routes calls to the PSTN gateway.
4. Define the PSTN gateway in the new SIPG M/M command.
5. Build the SIP trunk card and allocate SIP trunk ports.
6. Activate the SIP trunks.
7. Define a route that steers calls to the SIP Trunk.
Licensed SIP Trunks and SIP Destinations
To view the man-machine tables required to build a SIP trunk to a PSTN gateway, the
feature must be enabled by Aastra installation personnel.
A maximum of 100 SIP Trunk Gateways can be provisioned per Pointspan system. SIP
Gateway trunks are licensed per SIP port, not by the individual gateway. A SPN VoIP
license can be applied as a SPN SIP Terminal, SPN Generic SIP Terminal, SPN
Integrated Gateway Trunk circuit.
For example, a customer requires an AudioCodes gateway with 1 PRI span with 23 ISDN
trunk circuits, an AudioCodes MediaPack with 2 FXS Analog stations and 7 SIP
Terminals; 32 SPN VoIP licenses are required.
Define the System Wide Domain Name in SPAR
The SYSTEM-WIDE SIP DOMAIN NAME is typically the same name as the “SPN
PROXY IP ADDR” parameter in PHYS PARTITION.
Define the system-wide sip domain name:
SELECT COMMAND => spar
SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES => d
ENTER DISPLAY TYPE or ?.....................S => u
08/13/08
15:19:03
CDM...SYSTEM-WIDE SIP DOMAIN NAME........192.168.6.6
Aastra - 2808-001
25
Change PSWD Permissions on Table SIPG
From PointSpan man-machine table PSWD, change the permissions on the SIPG
command for terminal T0 and password P0 to enable display, print, update and titles.
SELECT COMMAND => pswd
SELECT MODE: PRINT, DISPLAY, UPDATE => u
UPDATE MODE: C=Create,M=Modify,D=Delete => m
TERMINAL OR PASSWORD # or Return=END or ? => p0
PASSWORD NAME........................EADS01AZ =>
MAX ALLOWED "LEVEL" NUMBER:.................3 =>
COMMAND MNEMONIC or - ....................... => sipg
ENTER -=ALL; N=COMMAND NOT ALLOWED; <CR>=NO CHANGE
1,2,3= ADD THESE; R,3,5= REMOVE THESE. (modify only)
ALLOWED
------NO
NO
NO
NO
OPTION #
-------1
2
3
4
DESCRIPTION OF SUBCOMMAND
------------------------DISPLAY
PRINT
UPDATE
TITLES
SELECT SIPG OPTION NUMBERS or ? ............. => SELECT SIPG OPTION NUMBERS or ? ............. =>
COMMAND MNEMONIC or - ....................... =>
** VERIFY DISPLAY
** MMP PASSWORD 0: "EADS01AZ" PERMISSIBILITY
09/09/08 14:35:27
** MAXIMUM "LEVEL" ALLOWED BY PASSWORD: 3
ABVD........PRINT DISPLAY UPDATE COPY
ACD.........PRINT DISPLAY UPDATE TITLES CHANGE
ACDC........PRINT DISPLAY UPDATE TITLES
ACDR........PRINT DISPLAY CLEAR ADMIN
ACLK........(No modes defined for this command)
ACUP........PRINT DISPLAY UPDATE FORMAT SAVE RESTORE
AGID........PRINT DISPLAY UPDATE RESTORE
AIDD........PRINT DISPLAY UPDATE
AIP.........PRINT DISPLAY UPDATE
ALRM........(No modes defined for this command)
AMD.........PRINT DISPLAY
AMSG........PRINT DISPLAY UPDATE SEARCH
APRG........PRINT DISPLAY UPDATE
ARCT........PRINT DISPLAY UPDATE SEARCH TITLES
ASRP........PRINT DISPLAY CLEAR
ATTR........PRINT DISPLAY UPDATE
AVNT........PRINT DISPLAY BUILD CANCEL UPDATE
BTNS........PRINT DISPLAY UPDATE SEARCH TITLES
CAC.........PRINT DISPLAY UPDATE
CACR........PRINT DISPLAY CLEAR
RETURN CONTINUES DISPLAY..... => y
DOES UPDATE VERIFY ? => y
TABLE CHANGE PERFORMED
** MMP NOTE: SIGN-ON REQUIRED TO ACTIVATE CHANGE
TERMINAL OR PASSWORD # or Return=END or ? => t0
COMMAND MNEMONIC or - ....................... => sipg
ENTER -=ALL; N=COMMAND NOT ALLOWED; <CR>=NO CHANGE
1,2,3= ADD THESE; R,3,5= REMOVE THESE. (modify only)
ALLOWED
------NO
NO
NO
NO
26
OPTION # DESCRIPTION OF SUBCOMMAND
-------- ------------------------1
2
3
4
DISPLAY
PRINT
UPDATE
TITLES
Aastra – 2808-001
SELECT SIPG OPTION NUMBERS or ? ............. => SELECT SIPG OPTION NUMBERS or ? ............. =>
COMMAND MNEMONIC or - ....................... =>
** VERIFY DISPLAY
** MMP TERMINAL 0: "C R"
PERMISSIBILITY
09/09/08 14:35:45
ABVD........PRINT DISPLAY UPDATE COPY
ACD.........PRINT DISPLAY UPDATE TITLES CHANGE ADMIN
ACDC........PRINT DISPLAY UPDATE TITLES
ACDR........PRINT DISPLAY CLEAR ADMIN
ACLK........(No modes defined for this command)
ACUP........PRINT DISPLAY UPDATE FORMAT SAVE RESTORE
AGID........PRINT DISPLAY UPDATE RESTORE
AIDD........PRINT DISPLAY UPDATE
AIP.........PRINT DISPLAY UPDATE
ALRM........(No modes defined for this command)
AMD.........PRINT DISPLAY
AMSG........PRINT DISPLAY UPDATE SEARCH
APRG........PRINT DISPLAY UPDATE
ARCT........PRINT DISPLAY UPDATE SEARCH TITLES
ASRP........PRINT DISPLAY CLEAR
ATTR........PRINT DISPLAY UPDATE
AVNT........PRINT DISPLAY BUILD CANCEL UPDATE
BTNS........PRINT DISPLAY UPDATE SEARCH TITLES
CAC.........PRINT DISPLAY UPDATE
CACR........PRINT DISPLAY CLEAR
CARD........PRINT DISPLAY UPDATE MOVE
RETURN CONTINUES DISPLAY..... => y
** MMP NOTE: SIGN-ON REQUIRED TO ACTIVATE CHANGE
TERMINAL OR PASSWORD # or Return=END or ? => @
SELECT COMMAND => @
Create the SIP Trunk Group to Route Calls to the PSTN Gateway
Build the SIP Trunk Group to send/receive calls to the PSTN Gateway:
SIP Trunk Group Parameter Descriptions
Parameter
Description
TRUNK GROUP TYPE:
Build the Trunk Group as a SIP Trunk.
SIP "From:" URI: U, A, S,
T or ?
Set to:
S = Send Calling Party Name/Number using "sip:" URI
If the Calling Party name and number is available, the
SPN will send it to the gateway in the TO header using the
“sip:” URI format.
SIP P-ASSERTEDIDENTITY:
Set to:
AB = Send SIP "P-Asserted-Identity:" with "sip:" & "tel:"
URIs
The P-Asserted-Identity header field is used among trusted
SIP entities (typically intermediaries) to carry the identity
of the user sending a SIP message as it was verified by
authentication.
Aastra - 2808-001
27
Parameter
Description
P-Asserted-Identity: "Joe Smith"
<sip:[email protected]>
A P-Asserted-Identity header field value MUST consist of
exactly one name-addr or addr-spec. There may be one or
two P-Asserted-Identity values. If there is one value, it
MUST be a sip, sips, or tel URI. If there are two values,
one value MUST be a sip or sips URI and the other MUST
be a tel URI. It is worth noting that proxies can (and will)
add and remove this header field.
The P-Preferred-Identity header field is used from a user
agent to a trusted proxy to carry the identity the user
sending the SIP message wishes to be used for the PAsserted-Header field value that the trusted element will
insert.
P-Preferred-Identity: "Joe Smith"
<sip:[email protected]>
A P-Preferred-Identity header field value MUST consist of
exactly one name-addr or addr-spec. There may be one or
two P-Preferred-Identity values. If there is one value, it
MUST be a sip, sips, or tel URI. If there are two values,
one value MUST be a sip or sips URI and the other MUST
be a tel URI. It is worth noting that proxies can (and will)
remove this header field.
SIP DELAYED MEDIA:
Set to:
UN = Use only if necessary (when actual call originator is
known when INVITE msg is sent)
This field is required to establish early cut-thru on various
call types (ACD, IXL…).
SELECT COMMAND => grps;u;c;900
ENTER GROUPS TYPE or ?....................... => tgrp
ENTER TITLE:.....____________________________________________ => SIP Trunk to PSTN
Gateway
***...TRUNK GROUP........................900
TRUNK GROUP TYPE: or ?....................UNV => ?
UNV
DID
DISA
TERM
ATDC
OUTG
4WEM
MAIL
PAGE
ANCM
PRI
MVCF
DIPN
UTIL
28
-
UNIVERSAL
DIRECT INWARD DIAL
DIRECT INCOMING SYSTEM ACCESS
TERMINATED DDCO (BOTHWAY)
INCOMING TERMINATED TO ATTENDANT
GROUND START OUTGOING
4 WIRE E&M (BOTHWAY)
InteMail SYSTEM TRUNKS
PAGING SYSTEM TRUNKS
ANNOUNCEMENT SYSTEM TRUNKS
PRIMARY RATE INTERFACE TRUNKS
MOVACS CALL FACILITIES
DIPN TRUNKS
UTILITY TRUNKS
Aastra – 2808-001
SIP
- SIP TRUNKS
TRUNK GROUP TYPE: or ?....................UNV => sip
TRUNK CLASS: D=DIAL REPTG TIE; A=AUTO IN TIE;
L=LOCAL CO; F=FX; W=WATS; E=EQUAL ACC
R=REMOTE ACCS..................L =>
USER GROUP NUMBER:........................... => 1
CONTENTS OF NATIONAL CALLING PARTY # or ?...U =>
SELECT USER GROUP CALLING PARTY # or ?....... => 2
DISPLAY CALLING PARTY NUMBER or ?..Y/N......N => y
PRIVATE NETWORK: Y=YES; N=NO................N =>
OAI ASSOCIATED MEMBER: Y=YES; N=NO..........N =>
FAILURE THRESHOLD: 1-3, N=NONE..............3 =>
RESEIZE DELAY TIME IN 50MSEC INCREMENTS.....0 =>
MINIMUM HOLD TIME IN SECONDS................0 =>
TRUNK CALL HANDLING: I=INTERNAL; E=EXTERNAL.E =>
DISCONNECT SUPERVISION: Y=YES; N=NO.........Y =>
DIRECTION OF TRUNKS: B=BOTHWAY;
I=INCOMING ONLY; O=OUTGOING ONLY............B =>
IGNORE GLARE: Y=YES; N=NO...................N =>
DTMF PASSTHROUGH TIMING INDEX: 1-7,N or ?...N =>
INCOMING TRUNK TYPE: T=TERMINATED
D=DIALED AND DIRECT IN DIAL.................D =>
INCOMING CALL MESSAGE #: N = NONE...........N =>
ROUTING TYPE: NR, DN, E or ?...............NR =>
WHISPER MESSAGE SOURCE GROUP or ?...........N =>
NUMBER OF DID DIGITS TO COLLECT: 1-5........4 =>
DID PREFIX DIGITS: N=NONE..................N =>
TK GRP AUTH TYPE: A=APPEND; F=FILED; N=NONE.N =>
PRE-VALIDATE AUTHORIZATION: Y=YES; N=NO.....N =>
PREDEFINED LEVEL CODE: Code or ? N=NONE.....N =>
TIMEOUT TO ATTENDANT: Y=YES; N=NO...........N =>
CALLWAIT RINGBACK : Y=YES; N=NO.............N =>
TRUNK UPDATE CDR ON TRANSFER:
N=NO; F=FIRST TRANSFER; -=ALL TRANSFERS.....- =>
InteMail LAMP MESSAGE USER GROUP LIST:
USER GROUP (1-1000) or A=ALL or W=OWN........ => A
INTER-UGRP NNP USER GROUP LIST:
USER GROUP (1-1000) or A=ALL or W=OWN........ => A
NIGHT DIRECTORY NUMBER: N=NONE..............N =>
STATION CALL RESTRICTION ENABLED: Y/N.......N =>
NETWORK PLAYS BUSY SIGNAL: Y or N............ => y
NETWORK PLAYS REORDER: Y=Yes N=No...........Y => y
TRUNK SELECTION: L=LONGEST IDLE;
T=TOP DOWN; B=BOTTOM UP; D=LMS DISTRIBUTED..L => t
CALLING PARTY NUMBER: S; A; D or ?..........S =>
CALLING PARTY NAME: Y; N; or ?..............Y =>
ON-NET CALL: CALLING PARTY # SELECT or ?....D =>
OFF-NET CALL: CALLING PARTY # SELECT or ?...D => i
SIP "From:" URI: U, A, S, T or ?...........U => ?
Select the contents of the SIP "From:" URI:
U = Send Unavailable Calling Party Name/Number
Send URI: sip:UNAVAILABLE@(Originator Domain Name)>
A = Send Anonymous Calling Party Name/Number
Send URI: "Anonymous" <sip:[email protected]>
S = Send Calling Party Name/Number using "sip:" URI
T = Send Calling Party Number ONLY using "tel:" URI
SIP "From:" URI: U, A, S, T or ?...........U => s
SIP P-ASSERTED-IDENTITY: or ?..............N => ?
N
AS
AT
AB
PS
Aastra - 2808-001
=
=
=
=
=
Do NOT Send
Send SIP "P-Asserted-Identity:" with "sip:" URI
Send SIP "P-Asserted-Identity:" with "tel:" URI
Send SIP "P-Asserted-Identity:" with "sip:" & "tel:" URIs
Send SIP "P-Preferred-Identity:" with "sip:" URI
29
PT = Send SIP "P-Preferred-Identity:" with "tel:" URI
PB = Send SIP "P-Preferred-Identity:" with "sip:" & "tel:" URIs
SIP P-ASSERTED-IDENTITY:
SIP DELAYED MEDIA:
or ?..............N => ab
or ?....................N => ?
SIP Delayed Media (SDP in ACK msg instead of INVITE msg)
N = Do NOT Use (send SDP in INVITE msg)
UN = Use only if necessary (when actual call
originator is known when INVITE msg is sent)
UA = Use always (send SDP in ACK msg)
SIP DELAYED MEDIA:
or ?....................N => un
DIAGNOSTIC PARAMETERS: Y or N...............N =>
Define the PSTN Gateway in the new SIPG Command
Create an entry in SIPG for the PSTN Gateway:
Parameter Descriptions
SIPG Parameter
Description
SIP GATEWAY NAME
User name used for Registration and
Basic/Digest authentication with a Proxy /
Registrar server. The parameter doesn't have a
default value (empty string).
(AudioCodes parameter SIP
PARAMS/USERNAME.)
30
GATEWAY IP ADDRESS:
The IP address assigned to the AudioCodes
Gateway.
ASSOCIATED SPN PARTITION:
The SPN partition used to interface with the
AudioCodes Gateway.
USER GROUP NUMBER:
The user group used to process incoming calls
from the AudioCodes trunk.
SEND ";user=phone" IN SIP URIs:
Determines whether to add 'user=phone' string in
SIP URI. The "user=phone" parameter is a hint
that the part to the left of the '@' sign is actually
a phone number, in case there are SIP users
whose names happen to consist of all digits.

No = 'user=phone' string isn't used in SIP
URI.

Yes = 'user=phone' string is part of the SIP
URI (default).
Aastra – 2808-001
SIPG Parameter
Description
TRUNK GROUP
IDENTIFICATION USE:
Determines whether the SIP trunk group
parameter, which specifies the Trunk Group to
which the call belongs, is used.
SIP REGISTRATION:

N - Not Enabled = The 'tgrp' parameter isn't
used (default).

R - Only Receive and Use Trunk Group IDs
from Gateway = The Trunk Group number is
received in the 'tgrp' parameter value in the
Contact header of incoming SIP messages. If
a Trunk Group number is not associated with
the call, the 'tgrp' parameter isn't included. A
'tgrp' value is not sent in outgoing messages.
The received ‘tgrp’ value is used to entry
into table TM9.

S - Only Send Trunk Group IDs to Gateway
= The Trunk Group number is added to the
'tgrp' parameter value in the Contact header
of outgoing SIP messages. If a 'tgrp' value is
specified in incoming messages, it is
ignored. For outgoing SIP messages to
AudioCodes, if the Request-URI includes a
'tgrp' parameter, AudioCodes routes the call
according to that value (if possible). If the
Contact header includes a 'tgrp' parameter, it
is copied to the corresponding outgoing
messages in that dialog.

B - Send/Receive Trunk Group IDs to/from
Gateway = The functionality of outgoing SIP
messages is identical to the functionality
described in options (R and S).
Implicit or Explicit registration received from
AudioCodes:

N - No SIP Registration (Implicit) = As part
of an implicit registration, Pointspan initiates
a service check to determine if the SIP
gateway is available to send or receive calls
across the gateway’s SIP trunks.
The service check consists of sending a SIP
OPTIONS message. If the SIP gateway
successfully responds to the message, the SIP
gateway is considered in-service; therefore,
Pointspan marks the SIP gateway as registered.
The trunks associated with the gateway are idled
and placed into the appropriate SIP trunk group.
Aastra - 2808-001
31
SIPG Parameter
Description
When a gateway is out-of-service pending a
successful implicit registration, Pointspan does
NOT send any calls to the gateway; however,
any SIP INVITE received from the gateway
causes Pointspan to complete the implicit
registration (marking the gateway as in-service
and registered); Pointspan then accepts and
processes the received call normally.

G - SIP Registration By SIP Gateway
(Explicit Registration) = The SIP gateway
must send a SIP REGISTER message to
Pointspan to initiate an explicit registration.
Upon receiving and validating the request,
Pointspan marks the SIP gateway as
registered and responds with a 200 OK to the
request.
When a gateway is out-of-service pending a
successful explicit registration, Pointspan does
NOT send any calls to the gateway; however,
any SIP INVITE received from the gateway
causes Pointspan to place the SIP trunks inservice ONLY for received calls; Pointspan then
accepts and processes the received call normally.
Pointspan then continues to wait for the explicit
registration before routing outbound calls to the
gateway.
Once registered (either implicitly or explicitly),
Pointspan periodically (once every 15 seconds)
performs a service check on each in-service SIP
gateway to insure the gateway remains inservice.
When the periodic service check fails or an
existing explicit SIP registration expires and is
not refreshed by the gateway, Pointspan
generates an alarm and places all SIP trunks
associated with the SIP gateway out-of-service.
However, existing calls to Pointspan stations or
trunks supporting disconnect supervision remain
active until terminated by the remaining party in
the call.
The in-service status of the SIP gateway does not
affect the operation of any SIP station assigned
to that gateway. SIP stations, whether standalone
or behind a SIP gateway, use a separate SIP
registration process for determining eligibility to
receive calls.
32
Aastra – 2808-001
SIPG Parameter
Description
SENT AUTHENTICATION NAME:
Defines the user name that is used in the From
and To headers in REGISTER messages.
AudioCodes parameter SIP PARAMS/
GWRegistrationName. If no value is specified
(default) for this parameter, the UserName
parameter is used instead.
VALIDATE SIP
AUTHENTICATION PSWD:
Authenticate and verify the password received
from AudioCodes.
SIP AUTHENTICATION
PASSWORD:
The password used to authenticate requests
received from the AudioCodes gateway.
(AudioCodes parameter SIP PARAMS/
PASSWORD.)
GATEWAY URI USER NAME:
The username used for Registration and
Basic/Digest authentication with a Proxy /
Registrar server. The parameter doesn't have a
default value (empty string).
(AudioCodes parameter SIP
PARAMS/USERNAME.)
Aastra - 2808-001
GATEWAY URI DOMAIN NAME:
The registrar domain name. If specified, the
name is used as the Request-URI in REGISTER
messages. If it isn't specified (default), the
Registrar IP address, or Proxy name or IP
address is used instead. The valid range is up to
49 characters.
SIP GATEWAY SUPPORTS
"REPLACES":
Enables blind transfer. Blind transfer is
performed after we have a call between A and B,
and party A decides to immediately transfer the
call to C without speaking with C. The result of
the transfer is a call between B and C (just like
consultation transfer only skipping the
consultation stage).
INCOMING CALL DESTINATION SELECTION
TABLE:
Associates inbound calls from a trunk group on
the AudioCodes Gateway to a trunk group on
PointSpan. For example, a PSTN call is received
on AudioCodes trunk group (for example: 3) and
sent to PointSpan. PointSpan routes the call as if
it enter the switch on PointSpan’s trunk group
(for example: 900).
33
OUTBOUND CALL DESTINATION TRANSLATION
TABLE:
Associates outbound calls from a trunk group on
the PointSpan to a trunk group on AudioCodes
Gateway. For example, a PSTN call is sent from
PointSpan’s trunk group (for example: 900) to
AudioCodes; when AudioCodes receives the call
it will route the call to the PSTN on trunk group
(for example: 3).
SELECT COMMAND => sipg
SELECT MODE: DISPLAY, PRINT, UPDATE, TITLES => u
UPDT MODE: C-Create,M-Modify,D-Delete........ => c
SIP GATEWAY #: or ?.......................... => 3
ENTER TITLE:.....____________________________________________ => AudioCodes 1
Gateway
SIP GATEWAY NAME: or ?....................... => TB1AC1
GATEWAY IP ADDR: or ?........................ => 192.168.6.40
ASSOCIATED SPN PARTITION NUMBER.............. => 4
USER GROUP NUMBER or ?....................... => 1
SEND ";user=phone" IN SIP URIs: Y/N or ?....N => y
TRUNK GROUP IDENTIFICATION USE: or ?........N => ?
SELECT USE OF TRUNK GROUP IDENTIFICATION:
N - Not Enabled - Do Not Send Trunk Group IDs
or Use Received Trunk Group IDs
R - Only Receive and Use Trunk Group IDs from Gateway
S - Only Send Trunk Group IDs to Gateway
B - Send/Receive Trunk Group IDs to/from Gateway
TRUNK GROUP ID CONSISTS OF INGRESS and/or EGRESS
TRUNK GROUP (";tgrp=") and TRUNK-CONTEXT (";trunk-context=")
TRUNK GROUP IDENTIFICATION USE: or ?........N => b
SIP REGISTRATION: G or N....................N => N
Enter:
SIP Registration:
N = No SIP Registration
G = SIP Registration By SIP Gateway
SENT AUTHENTICATION NAME: or ?............... => TB1AC1
***...RECEIVED AUTHENTICATION NAME.......TB1AC1
VALIDATE SIP AUTHENTICATION PASSWORD: or ?..Y => y
SIP AUTHENTICATION PSWD...................... => TB1AC1PASS
SIP GATEWAY URI USER NAME: or ?............................. => TB1AC1
SIP GATEWAY URI DOMAIN NAME: or ?............ => NONE
SRP...SIP GATEWAY SUPPORTS "REPLACES".... YES => y
GATEWAY GROUP
POINTSPAN GROUP
INCOMING CALL - DESTINATION SELECTION TABLE..
ACTION: S=SHOW; R=REMOVE; A=ADD, return=END..
INC CALL - DESTINATION SELECTION TABLE..
SIP GATEWAY TRUNK GROUP NUMBER...............
POINTSPAN SIP TRUNK GROUP NUMBER.............
INCOMING CALL - DESTINATION SELECTION TABLE..
ACTION: S=SHOW; R=REMOVE; A=ADD, return=END..
=> a
=> 3
=> 900
=>
OUTBOUND CALL - DESTINATION TRANSLATION TABLE..
ACTION: S=SHOW; R=REMOVE; A=ADD, return=END.. => a
34
Aastra – 2808-001
OUTB CALL - DESTINATION TRANSLATION TABLE..
POINTSPAN SIP TRUNK GROUP NUMBER............. => 900
SIP GATEWAY TRUNK GROUP NUMBER............... => 3
OUTBOUND CALL - DESTINATION TRANSLATION TABLE..
ACTION: S=SHOW; R=REMOVE; A=ADD, return=END.. =>
AudioCodes 1 Gateway
GNM...SIP GATEWAY NAME...................TB1AC1
IPA...GATEWAY IP ADDRESS.................192.168.6.40
ASP...ASSOCIATED SPN PARTITION...........4
UGP...USER GROUP NUMBER..................1
SIR...INVITE RESPONSE CODE TABLE NUMBER..DFLT
UPH...SEND ";user=phone" IN SIP URIs.....YES
TGS...TRUNK GROUP IDENTIFICATION.........SEND/RECEIVE IDs
SRG...SIP REGISTRATION...................NO Explicit SIP Registration
SAN...SENT AUTHENTICATION NAME........... TB1AC1
***...RECEIVED AUTHENTICATION NAME.......
SAD...VALIDATE SIP AUTHENTICATION PSWD...YES
SPW...SIP AUTHENTICATION PASSWORD........ TB1AC1PASS
......CURRENT PASSWORD VERSION...........1
SUN...GATEWAY URI USER NAME.............. TB1AC1
SDN...GATEWAY URI DOMAIN NAME............
SRP...SIP GATEWAY SUPPORTS "REPLACES"....YES
ICP...INC CALL - CALLING PARTY SLCT TBL..UNASSIGNED
IDT...INC CALL - DESTINATION SLCT TBL....2
GATEWAY GROUP
POINTSPAN GROUP
3
900
OCP...OUTG CALL - CALLING PARTY XLTN TBL.UNASSIGNED
ODT...OUTG CALL - DESTINATION XLTN TBL...4
POINTSPAN GROUP
GATEWAY GROUP
900
3
Build the SIP Trunk Card and Allocate SIP Trunk Ports
Build a SIP Trunk card and allocate SIP trunk ports. If the gateway has 23 ports (for
example, a PRI), then build 23 ports on the card.
SELECT COMMAND => card
SELECT MODE: PRINT, DISPLAY, UPDATE, MOVE =>
UPDT MODE: C-Create M-Modify D-Delete P-Copy.
ENTER LOCATION or ?..........................
CARD TYPE or ?...............................
SIPS....SIP STATION
u
=> c
=> 11.1.4
=> ?
SIPT....SIP TRUNK
CARD TYPE or ?............................... => sipt
*** VERIFY DISPLAY ***
***...CARD TYPE..........................SIPT
Aastra - 2808-001
35
** NOTE: SIP TRUNK PORTS MUST BE CREATED SEPARATELY **
ENTER LOCATION or ?.......................... => 11.1.4.1
# CONSECUTIVE/IDENTICAL SIP TRUNKS TO BUILD.. => 23
CREATING SIP
74 of 256
LICENSED
***...SIP TRUNK........PORT 011.1.04.01
TRUNK GROUP NUMBER...........................
SIP GATEWAY NUMBER...........................
CLASS OF SERVICE.............................
OAI ASSOCIATED MEMBER: Y=YES; N=NO..........N
NIGHT DIRECTORY NUMBER: N=NONE..............N
=> 900
=> 1
=> 1
=>
=>
***...SIP TRUNK........PORT 011.1.04.01
***...USER GROUP NUMBER..................1
***...DIRECTION..........................BOTHWAY
TGF...TRUNK GROUP NUMBER.................900
SGF...SIP GATEWAY NUMBER.................1
COS...CLASS OF SERVICE...................1
OAM...OAI ASSOCIATED MEMBER..............NO
NDN...NIGHT ANSWER DIRECTORY.............NONE
Activate the SIP Trunks
Put the SIP trunks into service using the CFG command. After the trunk is built, it comes
up in an “INACTIVE - Waiting for SPN to Initialize” state. Place the trunk in-service via
the “I” command and the state changes to “INACTIVE - Waiting for SPN to Contact
Gateway” state. After the SPN is able to communicate with the gateway, the state
becomes “ACTIVE”.
CFG/SGW
SELECT COMMAND => cfg
SELECT SUBCOMMAND or ?....................... => sgw
SIP GATEWAY # or - or ?...................... => P, D, I, O, F or ?........................... => d
Man-Machine T0
SIP GATEWAY STATUS DISPLAY
GATEWAY NBR
----------1
09/09/08
System Console
15:12:02
STATUS
-------------------------------------------------INACTIVE - Waiting for SPN to Initialize
P, D, I, O, F or ?........................... => i
CFG REQUEST COMPLETE
P, D, I, O, F or ?........................... => d
Man-Machine T0
GATEWAY NBR
----------1
09/09/08
System Console
15:13:33
STATUS
-------------------------------------------------INACTIVE - Waiting for SPN to Contact Gateway
P, D, I, O, F or ?........................... =>
36
Aastra – 2808-001
SIP GATEWAY # or - or ?...................... => P, D, I, O, F or ?........................... => d
08/26/08
GATEWAY NBR
----------1
15:36:24
STATUS
-------------------------------------------------ACTIVE
P, D, I, O, F or ?........................... => ?
P
D
I
O
F
=
=
=
=
=
PRINT
DISPLAY
IN SERVICE
OUT OF SERVICE
FORCE OUT OF SERVICE
Define a Route to Steer Calls to the SIP Trunk
Refer to the “Pointspan System Database Administration” to create a route to place a call
to the SIP trunk group.
The following is an example route that was used to send calls to trunk group 900. In this
example, the user dialed 91(901)888-5001 to out pulse digits 5001 on the SIP trunk.
UGRP/FDD
SELECT COMMAND => ugrp;d;1;fdd
** USER GROUP
1 SHARES FDDs WITH OTHER USER GROUP FDDs
DISPLAY THE SHARING USER GROUPS?: Y=Yes; Return=No... =>
Primary User Group
** FIRST DIGIT DISPOSITION FOR USER GROUP# 1
08/25/08
1....FIRST DIGIT 1 FIXED LENGTH DIR. NUM.
4 DIGITS
4 DIGITS
4 DIGITS
4 DIGITS
4 DIGITS
4 DIGITS
4 DIGITS
8....FIRST DIGIT 8 BELL RECOMMENDED........AUTH
NORMAL
9....FIRST DIGIT 9 BELL RECOMMENDED........NO AUTH NORMAL
0....FIRST DIGIT 0 ATTENDANT
17:04:59
NNP...NNP FIRST DIGITS.......................2 3 4 5 6 7 8 9
3DS...3 DIGIT SPEED NUMBER FIRST DIGITS......
4DS...4 DIGIT SPEED NUMBER FIRST DIGITS......
ENTER DIALING LEVEL, RETURN = END or ?....... => @
END OF DISPLAY
UGRP/NPA
SELECT COMMAND => ugrp;d;1;npa
** USER GROUP
1 SHARES NPAs WITH OTHER USER GROUP NPAs
DISPLAY THE SHARING USER GROUPS?: Y=Yes; Return=No... =>
NPA No., C, ? or Return=END.................. => 1
Unity npa
** NPA ROUTING TABLE 1
** NPAs NOT SHOWN ARE BLOCKED
Aastra - 2808-001
USER GROUP 1
08/25/08
37
NPA TREATMENT
214-->RGN 72
333-->RGN 700
606-->RGN 777
819-->RGN 93
940-->RGN 40
END OF DISPLAY
NPA TREATMENT
222-->RGN 712
408-->RGN 10
707-->RGN 777
900-->RGN 97
972-->RGN 72
NPA TREATMENT
223-->RGN 82
469-->RGN 72
800-->RGN 72
901-->RGN 901
998-->RGN 95
NPA TREATMENT
301-->RGN 301
505-->RGN 72
817-->RGN 10
902-->RGN 902
999-->RGN 91
NPA No., C, ? or Return=END.................. => @
ROUT Command
SELECT COMMAND => rout;d;901
SIP Gateway
*** ROUTE GUIDE # 901
08/25/08
17:01:28
1 TRUNK GROUP 900
-- FRL: 0 -- PREFIX DIGIT STRING # 901
2 BUSYOUT
ROUTE GUIDE # or ?........................... => @
PDT Command
SELECT COMMAND => pdt;d;901
SIP Gateway
*** OFF-NET
PREFIX DIGIT TABLE # 901
1) DESTINATION NUMBER:
PLAN:
ISDN/TELEPHONY
TYPE:
SUBSCRIBER
OUTPULSE NUMBER TYPE: DIRECTORY
NUMBER: NO PREFIX DIGITS
08/25/08
PLUS
17:01:39
4 SIGNIFICANT DIGITS
PointSpan Utilities
Normal trunk utilities apply to the SIP trunks such as TUTL and MOS/MIS plus the new
CFG sub-command SGW.
Do not attempt to use the CFG;CRD command. To logically restart the SIP Gateway, use
the CFG;SGW command; to take individual ports in and out of service use the MOS/MIS
command management.
PointSpan Alarm
Verify the AudioCodes Gateway is up and ready to take calls – A PointSpan console
alarm SIPG-3790.
38
Aastra – 2808-001
CFG > SGW
Verify the status of the SIP trunk via the cfg;sgw command.
SIP GATEWAY # or - or ?...................... => P, D, I, O, F or ?........................... => ?
P
D
I
O
F
=
=
=
=
=
PRINT
DISPLAY
IN SERVICE
OUT OF SERVICE
FORCE OUT OF SERVICE
P, D, I, O, F or ?........................... => d
GATEWAY NBR
----------1
08/26/08
15:36:24
STATUS
-------------------------------------------------ACTIVE
MOS Display
Verify the status of the SIP trunk ports via the MOS command.
SELECT COMMAND => mos;d;;;;11.1.3
***
* ALL PORTS
***
CB.SH.CD.CT
----------011.1.03.01
011.1.03.03
011.1.03.05
011.1.03.07
(011.1.03.01 - 011.1.03.72) 08/26/08
TYPE
----TRNK
TRNK
TRNK
TRNK
STATUS
-----IDLE
IDLE
IDLE
IDLE
CB.SH.CD.CT
----------011.1.03.02
011.1.03.04
011.1.03.06
011.1.03.08
011.1.03.09 TRNK
IDLE
011.1.03.10
011.1.03.11 TRNK
IDLE
011.1.03.12
011.1.03.13 TRNK
IDLE
011.1.03.14
011.1.03.15 TRNK
IDLE
011.1.03.16
011.1.03.17 TRNK
IDLE
011.1.03.18
011.1.03.19 TRNK
IDLE
011.1.03.20
011.1.03.21 TRNK
IDLE
011.1.03.22
011.1.03.23 TRNK
IDLE
011.1.03.24
011.1.03.25 UNAS
011.1.03.26
011.1.03.27 UNAS
011.1.03.28
011.1.03.29 UNAS
011.1.03.30
011.1.03.31 UNAS
011.1.03.32
ENTER LOCATION, or ?......................... =>
Aastra - 2808-001
TYPE
----TRNK
TRNK
TRNK
TRNK
TRNK
TRNK
TRNK
TRNK
TRNK
TRNK
TRNK
UNAS
UNAS
UNAS
UNAS
UNAS
15:38:04
STATUS
-----IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
IDLE
39
TUTL Display
Verify the status of the SIP trunk ports via the MOS command.
SELECT COMMAND => tutl;d;d;900
DETAIL GROUP UTILIZATION REPORT:
GROUP # 900
SIP Gateway
GROUP:
TRUNK
------INCOMING-----PORT
STATUS
NO. %USAGE AVG.DUR.
011.1.03.01 IDLE
0 00.00 00:00:00
011.1.03.02 IDLE
0 00.00 00:00:00
011.1.03.03 IDLE
0 00.00 00:00:00
011.1.03.04 IDLE
0 00.00 00:00:00
011.1.03.05 IDLE
0 00.00 00:00:00
011.1.03.06 IDLE
0 00.00 00:00:00
011.1.03.07 IDLE
0 00.00 00:00:00
011.1.03.08 IDLE
0 00.00 00:00:00
011.1.03.09 IDLE
0 00.00 00:00:00
011.1.03.10 IDLE
0 00.00 00:00:00
011.1.03.11 IDLE
0 00.00 00:00:00
011.1.03.12 IDLE
0 00.00 00:00:00
011.1.03.13 IDLE
0 00.00 00:00:00
011.1.03.14 IDLE
0 00.00 00:00:00
011.1.03.15 IDLE
0 00.00 00:00:00
011.1.03.16 IDLE
0 00.00 00:00:00
011.1.03.17 IDLE
0 00.00 00:00:00
011.1.03.18 IDLE
0 00.00 00:00:00
011.1.03.19 IDLE
0 00.00 00:00:00
011.1.03.20 IDLE
0 00.00 00:00:00
011.1.03.21 IDLE
0 00.00 00:00:00
011.1.03.22 IDLE
0 00.00 00:00:00
011.1.03.23 IDLE
0 00.00 00:00:00
40
08/26/08
------OUTGOING-----NO. %USAGE AVG.DUR.
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
0 00.00 00:00:00
# OF
FAIL
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
15:42:33
REPORT
DURATION
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:02
03:18:06
03:18:06
03:18:06
03:18:06
03:18:06
03:18:06
Aastra – 2808-001
Chapter 3
911 Enhancements
The Pointspan SPN has supported E911 since its introduction with Pointspan release 5.
Additional 911 functionality enhancements have been provided with Pointspan release
5.2. These enhancements include:

OAI Call Information Message (OAI CIM) for SIP Device Registration

OAI Application Requested Call (OAI ARC) Update of the Pointspan Station
Emergency Associated Calling Party Number (EAC)

LLDP-MED Emergency Location Identification Number (ELIN) support

Emergency Location Identifier Determined by IP Address

#*9 Diagnostic to Speak Emergency Calling Party Number
Aastra - 2808-001
41
Chapter 3, 911 Enhancements
42
Aastra – 2808-001
Chapter 4
LLDP-MED
LLDP-MED Support for Aastra SIP Stations
The Aastra IP phones support Link Layer Discovery Protocol for Media Endpoint
Devices (LLDP-MED). LLDP-MED is designed for such things as:

Auto-discovery of LAN policies (such as VLAN, Layer 2 Priority and Diffserv
settings) leading to "plug and play" networking.

Extended and automated power management of Power over Ethernet endpoints.

Inventory management, allowing network administrators to track their network
devices, and determine their characteristics (manufacturer, software and hardware
versions, serial / asset number).
On the Aastra IP Phones, LLDP-MED performs the following:

Supports the MAC/PHY configuration (e.g. speed rate/duplex mode).

Supports VLAN info from the network policy; this takes precedence over manual
settings.

Allows you to enable/disable LLDP-MED if required.

Allows you to configure time interval between successive LLDP Data Unit
(LLDPDU) frames.

Allows LLDP packets to be received from the LAN port and allows them to reach the
PC Port.

Allows the phone to use the location information, Explicit Congestion Notification
(ECN) Emergency Location Identification Number (ELIN), sent by the Ethernet
switch, as a caller ID for making emergency calls.

Requires Aastra SIP Station firmware release 2.3. The Aastra SIP Station Firmware
release 2.3 will be released as SPN SIP Firmware Release 1.0.8.

Requires network infrastructure that supports LLDP-MED.
LLDP-MED Processing
Enabling LLDP-MED on a SIP station allows the station to receive network
configuration information from the Ethernet switch that it is connected to.
The LLDP-MED capability of the SIP station has no real-time impact on the call
processing of the Pointspan system.
Aastra - 2808-001
43
Chapter 4, LLDP-MED
LLDP-MED VLAN Auto-Discovery
The SIP phone discovers the VLAN information upon phone restart by negotiating the
LLDP-MED protocol with its network Ethernet switch prior to loading the Aastra.cfg and
MAC.cfg files. If a VLAN is found during the LLDP protocol negotiation, the VLAN
information programmed via the Pointspan station database and MAC.cfg file are ignored
by the SIP phone. The VLAN discovery settings are for Ethernet #0 interface of the SIP
phone.
Administrative Advantages
The LLDP-MED VLAN Auto-Discovery enhancement greatly simplifies VLAN
management for Moves, Adds and Changes (MACs). When LLDP-MED for VLAN is
enabled, the Pointspan database administrator is not required to provision the voice
VLAN characteristics of the SPN SIP station. The VLAN methodology for the voice
network can be established by the network administrator at installation and the Pointspan
SPN user does not need to be matched to a specific VLAN. The VLAN parameters are
discovered during SIP phone restart.
In addition, if a SIP terminal requires relocation to a new VLAN segment, the user
merely relocates their SIP Terminal and the VLAN settings are updated automatically.
Without LLDP-MED for VLAN in use, the user must coordinate the phone relocation
with the Pointspan database administrator, the Pointspan database must be updated at the
scheduled move time, the SIP phone must be rebooted to ‘pick-up’ the configuration
change, and it must be moved to the new location.
Emergency Location Identification Number (ELIN)
When ELIN is enabled for a SIP station and an emergency call is placed, Call Processing
extracts the ELIN provided by the SIP station and sends it as the Calling Party Number
when the call is originated to the emergency destination.
Transmission of ELIN by SIP Station
When an emergency call is originated from an ELIN enabled SIP station, it replaces the
Display Name in the From: header of the INVITE with the ELIN read from the Ethernet
switch it is connected to, based on a match-up of the “emergency string” in the aastra.cfg
file.
The Pointspan system supports an ELIN that consists of 10 to 16 numeric characters.
If the SIP station is enabled for ELIN, but an ELIN is not provided by the switch then the
SIP station sends in its normal Display Name in the From: header just as it would on a
normal non-emergency call. When an emergency call is made the ELIP, EAC, or Calling
Party number would be sent to the 911 operator in cases where the ELIN was not
available.
Processing of ELIN
When an emergency call is placed from a SIP station, Call Processing must determine if
the text provided in the Display Name is actually an ELIN. This is required because the
44
Aastra – 2808-001
SIP station could have ELIN enabled, but the ELIN on the connected Ethernet switch
may not be configured which would result in no ELIN being transmitted.
Call Processing assumes that an ELIN is provided by the SIP station on an emergency
call if all of the following conditions are true:

The SIP station has ELIN enabled in the Pointspan database,

The From: header Display Name is between 10 and 16 characters long,

All characters of the From: header Display Name are numeric (no spaces or special
characters)
When an ELIN is supplied by a SIP station placing an emergency call, Call Processing
uses the supplied ELIN as the Calling Party Number when placing the call to the PSAP.
If no ELIN is provided by the SIP station on an emergency call, then the station’s EAC
field is used as the Calling Party Number. If EAC is not configured for the station, then
the Calling Party Number is determined by the settings of the voice line and user group.
LLPD-MED Configuration
Aastra SIP Station Configuration File Parameters
There are 4 MAC/Aastra configuration file parameters for LLDP-MED.
Parameter
Description
MAC.cfg file parameters:
lldp
The lldp: configuration parameter is used by the SIP station to enable
and disable the LLDP-MED capability.
On the Pointspan system the lldp: parameter is stored in the MAC.cfg
file.
The lldp: parameter is controlled by the Man-Machine FONE command.
use lldp elin
Controls the use of ELIN by the SIP station. If use lldp elin: is enabled
then the SIP station sends in an ELIN when an emergency call is placed
from the SIP station. The ELIN used by the SIP station is received from
the connected Ethernet switch.
On the Pointspan system the lldp: parameter is stored in the MAC.cfg
file.
The lldp: parameter is controlled by the Man-Machine FONE command.
Aastra - 2808-001
45
Chapter 4, LLDP-MED
Aastra.cfg file parameters:
lldp interval
Used to control the transmission of LLDPDU (LLDP Data Unit) frames
by the SIP station. These LLDPDU frames publish information about
the SIP station to the network allowing network administrators to track
the SIP station and determine its characteristics (manufacturer, software
and hardware versions, and serial / asset number).
If the lldp interval is set to 0, then LLDPDU packet transmission is
disabled. A non-zero value indicates the number of seconds between
transmissions of the LLDPDU frames.
On the Pointspan system the lldp interval: parameter is stored in the
aastra.cfg file.
The lldp interval: parameter is not controlled by any Man-Machine
command.
emergency
dial plan
Digit strings matching the emergency dial plan to allow the phone to
detect an emergency call, such as 911, #*911.
On the Pointspan system the lldp interval: parameter is stored in the
aastra.cfg file.
The lldp interval: parameter is not controlled by any Man-Machine
command.
FONE Command for LLDP-MED
LLDP-MED is enabled for a SIP Station using the Man-Machine FONE command. There
are two new prompts in the FONE command associated with LLDP-MED.
When LLDP is enabled, the SIP station overrides the manually configured LAN settings
such as VLAN, Layer 2 Priority and Diffserv settings and uses the settings received from
the Ethernet switch.
When LLDP is enabled for a station, the FONE command still allows the administrator to
configure VLAN settings. However, LLDP will override VLAN settings for ethernet port
0 configured in the FONE command if they are different from what is received via
LLDP.
46
FONE
Paramater
Function
Description
LLD
Enables/Disables
LLDP-MED for the
station
This prompt enables the LLDP-MED
functionality for the SIP station.
Aastra – 2808-001
FONE
Paramater
Function
Description
ELI
Enables the use of
the Emergency
Location
Identification
Number (ELIN)
When LLDP is enabled, the SIP station has the
ability to read an Emergency Location
Identification Number (ELIN) from the Ethernet
switch to which it is connected, and send this
ELIN in as a calling party number when an
emergency call is placed from the SIP station.
The ELI prompt controls whether the SIP station
will send in the ELIN when an emergency call is
placed from the SIP station. The SIP station
determines if an emergency call is placed based
on the emergency dial plan configured in the
phone.
The user is prompted for ELI only if LLDP is
enabled (FONE;LLD = Yes).
Example:
SELECT COMMAND => FONE
UPDT MODE: C-Create M-Modify D-Delete........
ENTER PORT, LOCATION, WORK AT HOME or ?......
LOCATION (wiring directory):.................
CREATING SIP
15 of 500 LICENSED
ENTER PHONE TYPE DEFAULT SET ID or ?.........
ENTER PORT TYPE OR ?......................SIP
=> C
=> 2.2.1.50
=>
=>
=>
***...STATION......................PORT: 002.2.01.50
SIP PHONE TYPE: OR ?.....................@@@@ => A57I
BUTTON TEMPLATE NUMBER: 0=INDEX............. => 57
STATION USER GROUP NUMBER or ?............... => 1
ENABLE LLDP: Y=YES; N=NO or ?...............N => ?
Enable Link-Layer Discovery Protocol
Allows the SIP station to receive LAN
settings from the Ethernet switch.
Settings received from the Ethernet switch
WILL override the manually configured settings
if they are different.
ENABLE LLDP: Y=YES; N=NO or ?...............N => Y
***Note: LLDP will override VLAN settings for
ethernet port 0 configured in the FONE
command if they are different from what
is received via LLDP
ENABLE ELIN: Y=YES; N=NO or ?...............N => ?
(Note: Prompt appears only if LLDP is enabled)
Enable use of Emergency Location Identifier
Number (ELIN) as Calling Party Number for
emergency calls.
ENABLE ELIN: Y=YES; N=NO or ?...............N => Y
Aastra - 2808-001
47
Chapter 4, LLDP-MED
Emergency Location Identification by IP Address
Emergency Location Identification Determined by IP Address (ELIP) is a method used to
determine the calling party number to be used when a SIP station places an emergency
call. Emergency Location Identification Determined by IP Address (ELIP) is a method
used to determine the calling party number to be used when a SIP station places an
emergency call. ELIP can be used when a customer's LAN infrastructure doesn't have the
capability of using LLDP-MED and the customer can section off groups of phones by
static IP or controlled DHCP ranges.
When a SIP station enabled with ELIP places an emergency call, the Pointspan system
searches a database to map the SIP station’s IP address to an Emergency Location
Identifier to be used as the calling party number. The IP address provided by the SIP
station in the Authentication/Registration process is used for this functionality.
The new ELIP Man/Machine command is used to configure and maintain a database of
IP address ranges used by the SIP stations of the Pointspan system. The database
associates each range of addresses to an Emergency Location Identifier.
Enable ELIP for a SIP Station
Emergency Location by IP Address is enabled for a SIP station using the ELP option of
the FONE command:
Emergency Location Identification by IP Address.....N=> Y
.
.
ELP...Emergency Location Identification by IP Address...YES
Manage Emergency Location Identifiers for IP addresses
Emergency Location Identifiers for IP addresses are managed using the new ELIP
command that provides the following functions:

Define an Emergency Location Identifier for an IP address range.

Delete an Emergency Location Identifier for an IP address range.

Update the Emergency Location Identifier for an IP address range.

Display IP address ranges and Emergency Location Identifiers
Define an Emergency Location Identifier for an IP address range
To define an emergency location identifier for an IP address range, the starting IP address
and ending IP address of the range and a Location Identifier must be specified.
The starting and ending IP addresses can be the same to define a single address range.
The Location Identifier can be from 1 to 16 digits in length.
SELECT COMMAND => ELIP
UPDT MODE: C-Create M-Modify D-Delete........=> C
48
Aastra – 2808-001
ENTER
ENTER
ENTER
ENTER
FIRST IP ADDRESS IN RANGE .............=> 10.70.102.100
LAST IP ADDRESS IN RANGE .............=> 10.70.102.199
EMERGENCY LOCATION IDENTIFIER .........=> 4693653226
FIRST IP ADDRESS IN RANGE .............=>
START IP ADDRESS
10.70.102.100
END IP ADDRESS
10.70.102.199
LOCATION IDENTIFIER
4693653226
UPDATE VERIFY? =>
Delete Emergency Location Identifier for an IP Address Range
To delete an Emergency Location Identifier, the user must specify exactly the starting
and ending IP address of the range to be deleted.
UPDT MODE: C-Create M-Modify D-Delete........=> D
DELETE ALL OR ENTRY ....................... E=>
ENTER FIRST IP ADDRESS IN RANGE .............=> 10.70.102.100
ENTER LAST IP ADDRESS IN RANGE .............=> 10.70.102.199
START IP ADDRESS
10.70.102.100
END IP ADDRESS
10.70.102.199
LOCATION IDENTIFIER
4693653226
DELETE THIS ENTRY? =>
Modify Emergency Location Identifier for IP Address Range
Using the ELIP command the user can modify the Location Identifier for a specified IP
address range. The modify mode does not allow the user to modify the IP address range.
If the user wishes to modify the IP address range, then the existing range must be deleted
and the new range must be created.
UPDT MODE: C-Create M-Modify D-Delete........=> M
ENTER FIRST IP ADDRESS IN RANGE .............=> 10.70.102.100
ENTER LAST IP ADDRESS IN RANGE .............=> 10.70.102.199
START IP ADDRESS
END IP ADDRESS
10.70.102.100
10.70.102.199
LOCATION IDENTIFIER
4693653226
ENTER EMERGENCY LOCATION IDENTIFIER .........=> 4693653228
START IP ADDRESS
END IP ADDRESS
10.70.102.100
10.70.102.199
LOCATION IDENTIFIER
4693653228
UPDATE VERIFY? =>
Display Emergency Location Identifiers for IP Address Range
To display Location Identifiers for an IP address range the user may enter a ‘-‘ to display
all defined ranges or the user may enter a specific IP address and the address range
containing specified IP address will be displayed.
SELECT MODE: PRINT, DISPLAY, UPDATE => D
ENTER IP ADDRESS IN RANGE OR -.............=> -
Aastra - 2808-001
49
Chapter 4, LLDP-MED
START IP ADDRESS
END IP ADDRESS
10.70.102.100
10.70.108.200
10.90.65.100
10.70.102.199
10.70.108.250
10.90.80.100
LOCATION IDENTIFIER
4693653226
9032421880
7032817689
ENTER IP ADDRESS IN RANGE or -.............=> 10.70.108.222
START IP ADDRESS
END IP ADDRESS
LOCATION IDENTIFIER
10.70.108.200
10.70.108.250
9032421880
Emergency Location Identifier Determined by IP Address Operation
Process an Emergency Call
When an emergency call is placed from an ELIP enabled SIP station, Call Processing
determines the Calling Party Number to be used based on the IP address of the SIP
station that initiated the call.
The IP address of the SIP station is retrieved and a search is performed to determine if the
IP address of the SIP station is in a range defined in the ELIP database.
If the IP address is in a defined range of the ELIP database, the location identifier is
extracted and used as the calling party number for the emergency call.
If the IP address of the station is not in the ELIP database, then the SIP station EAC field
is used. If the Station EAC field is not defined, the calling party number is determined by
the normal processes using the settings of the voice line, user group, and SPAR.
Determine the IP Address of a SIP Station
The IP address used for ELIP processing is the registered or authenticated IP address of
the SIP station. The registered/authenticated IP address for a station can be viewed using
the SPN command and selecting the STATUS option.
The “registered IP address” is the IP address that is provided in the Contact URI of the
SIP REGISTER request.
The “authenticated IP address” is the IP address that is provided in the Contact URI of
the SIP request (the INVITE request for example) that is providing the authentication
credentials.
Prioritization Methods that Determine the Emergency Calling Party Number
The Pointspan system provides multiple options for determining an Emergency Location
Identifier. All of these methods can be enabled simultaneously on a single station. The
following lists each method in order of the priority in which they will be used when more
than one method is selected when an emergency call is originated:
50
Aastra – 2808-001
Method
Description
ELIN (Emergency Location
Identification Number) provided by
LLDP-MED
This method is used when all of the following
conditions have been met:
ELIP (Emergency Location
Determined by IP Address):
EAC (Emergency Associated Calling
Party Number):
Standard Calling Party Number based
on voice line, user group, or SPAR.

The calling station is SIP.

ELIN is enabled (FONE Command).

An ELIN is provided by the SIP station
when the emergency call is placed.
This method is used when the following

The calling station is SIP.

ELIN is not enabled (FONE Command) or
no ELIN was provided for the call.

ELIP is enabled (FONE Command).

The IP address of the calling station is in a
range defined in the ELIP database (ELIP
Command).
This method is used when the following

An EAC is defined for the originating
station (FONE Command).

The originating station is not SIP, or ELIN
and ELIP are not enabled (FONE
Command) or could not be used.
This method is used when all else fails.
Restrictions

The ELIP feature applies only to SPN SIP stations.

The Location Identifier can be up to 16 digits in length.

The ELIP feature does NOT apply to DPN stations.
#*9 Diagnostic to speak Emergency Location Identifier Number
A new diagnostic code has been added in Pointspan 5.2 that allows a user to hear the
emergency location identifier for a station by dialing #*9.
When #*9 is dialed on a station, call processing determines what the emergency location
identifier is for the station and speaks the identifier to the user. When the complete
identifier has been spoken the user will hear a zip-zip tone. If there is no emergency
location identifier defined for the station the user will simply hear a zip-zip tone.
#*9 is valid for any station in the Pointspan system.
Aastra - 2808-001
51
Chapter 4, LLDP-MED
52
Aastra – 2808-001
Chapter 5
IPMI Tool
Intelligent Platform Management Interface (IPMI)
The IPMI tool is introduced with the PS5.2 release. The IPMI tool resides on the SPN
server and is used by the ECS server to remotely reboot, power-on, and query the status
of the SPN server (power on or off).
IPMI Commands on the ECS
Step
Action
Result
To check the status (power on/off) of the SPN server from PointSpan ECS:
1.
From a TTY prompt on a PointSpan
ECS server:
Type spnstats
/ (OEMb)-> spnstats
SPN4A Power Status:
Chassis Power is on
SPN4B Power Status:
Chassis Power is on
Power status check completed
To power cycle the SPN server from PointSpan ECS:
The spnboot command will restart a server that is running, or it will start a server that is
powered off (the server must be connected to a power source).
1.
From a TTY prompt on a
PointSpan ECS server:
Type spnboot <spn server>
/ (OEMb)-> spnboot
version : 1.2.6.3
usage: spnboot x
x = SPN Identifier as defined in ibx/cfg/bmc.cfg
For example if "SPN3A 10.70.100.37" is in bmc.cfg,
you would enter "spnboot 3A" to reboot the SPN whose
BMC board has IP address 10.70.100.37.
/ (OEMb)-> spnboot 4A
SPN4A BMC IP 198.242.31.xxx Turning power on
ipmitool: Chassis Power Control: Up/On
Doing power cycle
ipmitool: Chassis Power Control: Cycle
Power Cycled.
Aastra - 2808-001
53
Chapter 5, IPMI Tool
54
Aastra – 2808-001
Chapter 6
SNMP Traps
SNMP Traps from PointSpan ECS
Simple Network Management Protocol (SNMP) is an internet-standard protocol for
managing devices on IP networks. The SNMP protocol specifies ways that a SNMP
manager can monitor and control an SNMP agent.
The PointSpan ECS SNMP Trap feature allows an ECS to send SNMP Traps to a
maximum of 4 licensed SNMP managers. A trap is an unsolicited message (such as an
error or status indication) the SNMP agent (the primary ECS) sends to an SNMP
manager.
The SNMP trap message contains the SNMP header information followed by the trap
variable binding information in Abstract Syntax Notation version 1 (ASN.1) format with
variables and values defined by a Management Information Base (MIB) document/file.
The variable binding portion of the trap contains a text string variable (as the alarm
would appear on the PointSpan Console Monitor screen) followed by subsequent
individual variables representing each part of the alarm in binary form.
A new database variable for alarm processing determines whether or not AIP processing
is to generate a SNMP trap message per specific alarm.
Error handling for the feature itself is limited to issuing a console monitor message. This
is not a standard alarm.
Requirements
SNMP traps will be generated on the IPLK interface of the ECS/NCS/RCS. This
will require either an SNMP manager on that subnet, a router or dual NIC server to
forward packets to the appropriate subnet. This requires the assistance of on site IT
personnel.
SNMP Trap Message Format and Content
The SNMP agent trap message packet is in SNMPv1 format.
Field
Name
Syntax
Description
Version
Standard SNMPv1
header format
Describes the SNMP version number of the
message.
0 = SNMPv1 format
Community
Aastra - 2808-001
Standard SNMPv1
header format
Identifies the SNMP community in which the
sender and recipient of this message are
located.
55
Field
Name
Syntax
Description
PDU Type
Standard SNMPv1
header format
Indicates the PDU type.
Enterprise
Standard SNMPv1
header format
An object identifier for a group, indicating the
type of object that generated the trap.
Agent IP
Address
Standard SNMPv1
header format

1 = Enterprise

205 = Aastra (registered with IANA)
The IP address of the SNMP agent that
generated the trap. This value is retrieved
from the Pointspan “siteid” information. The
default will be the “Primary addr:”. If this
address is not defined, the alternative address
will be derived from the “IPLK0(a/b) addr” of
the host ECS generating the SNMP traps.
If the IPLK0 address is used, the SNMP
Manager will receive different SNMP Agent
addresses depending on which Pointspan ECS
in primary.
56
Generic Trap
Standard SNMPv1
header format
A code value specifying the predefined
“generic” trap type.
Specific Trap
Standard SNMPv1
header format
A code value indicating an implementationspecific trap type.
Time Stamp
Standard SNMPv1
header format
The amount of time (in one-hundredth of a
second ticks) since the Pointspan ECS (SNMP
agent) last initialized or reinitialized the call
processing task.
Aastra – 2808-001
Aastra - 2808-001
Field
Name
Syntax
Variable
Bindings
Standard SNMPv1
format
Description
Data
Size
A set of variables (defined by
the MIB object):
80
bytes
Text string (as alarm would
appear on Console Monitor
screen).
4 bytes
Task name (4-character
pneumonic representing the task
generating the alarm.
1 byte
Alarm type (0=information,
1=Minor, 2=Major)
1 byte
Primary ECS (1=A, 2=B)
1 byte
Generating ECS (1=Primary,
2=Secondary)
2 bytes
Equipment Class (defined by
Alarm Information Processing
equates)
2 bytes
Alarm number
4 bytes
Time (in UTC format)
4 bytes
Data Word 0
4 bytes
Data Word 1
4 bytes
Data Word 2
4 bytes
Data Word 3
57
Man/Machine SNMP Parameters
The following Man/Machine commands are used to configure SNMP parameters:

SPAR – SNM

AIP – LSE
Command
Parameter
Description
SPAR
SNM
Number of licensed SNMP managers.
Example:
SELECT COMMAND => SPAR
SELECT MODE: PRINT, DISPLAY, UPDATE, TITLES
ENTER UPDATE TYPE or ?......................P
SPECIFY SYSTEM PARAMETER TO MODIFY or - or ?.
SNMP MANAGER: (1-4) or - or Return=END ......
SNMP MGR 2 IP ADDRESS : or ?..........1.2.3.4
SNMP MGR 2 PORT NUMBER: or ?..............162
SNMP MANAGER: (1-4) or - or Return=END.......
SNMP MGR 1 IP ADDRESS : or ?......10.70.10.38
SNMP MGR 2 IP ADDRESS : or ?..........1.2.3.4
SNMP MGR 2 PORT NUMBER: or ?...............62
SNMP MGR 3 IP ADDRESS : or ?.....11.222.33.44
SNMP MGR 3 PORT NUMBER: or ?.............1024
SNMP MGR 4 IP ADDRESS : or ?.................
SNMP MGR 4 IP ADDRESS : or ?.................
07/16/08
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
U
U
SNM
2
-
SNM
4
10.70.102.8
15:45:11
PAS...UNIT IN SECONDS FOR PAUSE.................3 SECONDS
D9D...DIRECT 911 DIALING........................YES


RNT...RECORDING NOTIFICATION TONE...............EVERY 30 SECONDS
SNM...SNMP MANAGER DESTINATIONS
MGR
--1
2
3
4
IP ADDRESS
---------------
PORT#
-----
10.70.10.38
1.2.3.4
11.222.33.44
10.70.102.8
162
162
1024
162
58
Aastra – 2808-001
AIP
LSE
Log report to SNMP. SNMP logging is already enabled
automatically for most Major and Minor alarms. The
AIP command is to manually activate an alarm that
does not already have SNMP logging activated. Only
CSC can make this update in AIP, it is password
protected. Any manual updates will need to be
documented by the customer as they will be removed
on a PointSpan retrofit to a new PointSpan release.
Customer must contact the Aastra CSC with the list of
updates after each retrofit.
Example:
SELECT COMMAND => AIP
SELECT MODE: PRINT, DISPLAY, UPDATE, SEARCH => U
ENTER ALARM NUMBER FOR UPDATING.............. => 341
*************************************************
*
*
*
Updates to P99 entries for: PFS, LCE,
*
* LDE, POP, CAN, CVT, OAL, SST, DRE, ATY,
*
* and STP can be temporary or permanent.
*
* Permanent updates are written to Q82.
*
*
*
* When the system is restarted, the P99 values *
* will revert to the values specified in Q82.
*
*
*
*
Updates to TC8 CHE (Call home) entry are
*
* written to the secondary and to the disk
*
* file (pfl 18)
*
*
*
*************************************************
AIP FIELD TO UPDATE, ? OR <RETURN>...........
CHE..CALL HOME
PFS..PROCESS ALARM FROM SECONDARY
LCE..LOG REPORT TO CONSOLE
LDE..LOG REPORT TO DISK
LSE..LOG REPORT TO SNMP
POP..POP THE STACK
CAN..CANCEL THE TASK
CVT..ALARM DISPLAY HEX OR DEC
OAL..GENERATED BY FIRMWARE
SST..STOP STATE STIM TRACE
DRE..DUMP REGISTERS TO FILE0009
ATY..ALARM TYPE
STP..SCRIPT TABLE POINTER
ACTIVATE LOGGING TO SNMP? Y/N...............N
ALARM DEFINITION
ALARM # = 341
TYPE = INF
EQUIPMENT CLASS = CARD
LOG
DISP
STOP CALL
CNSL DISK SNMP
MODE
SST
HOME
---- ---- -----------YES YES YES
HEX
NO
NO
=> ?
=> LSE
=> Y
=>
SUMMARY
SCRIPT
2NDMCU
-----NO
07/17/08
POP CANCEL
STACK TASK
----- ---NO
NO
REG.
AMD
--NO
16:46:05
O.ALRM
-----NO
SCRIPT
INDEX
----26
DOES UPDATE VERIFY ? =>
Aastra - 2808-001
59
Console Monitor SNMP Command
Console Monitor (CM) now has an “snmp” command.
Parameter
Description
Format:
snmp <parm>, where <parm> can be:
s
Stop sending SNMP messages.
r
Re-start sending SNMP messages. SNMP must have been previously
initialized for messages to be sent.
d
Display SNMP messages to console in a hex/text display.
q
Quit displaying SNMP messages to the console.
Console Messages
Console messages are issued during SNMP initialization and if an error occurs on a UDP
send.
Initialization Messages
The following are examples of initialization messages:
09:01:11 CP SNMP Successfully BINDed on local host
(1)
09:01:11 CP SNMP mgr 1 at 10.70.10.56, port 162 destination initialized.
(2)
(3)
(4)
09:01:11 CP SNMP mgr 4 licensed but no IP address defined
(5)

Message (1) indicates that the local socket was successfully opened and bound to a
port.

Messages (2), (3), (4) indicate that the destination message structures for managers 1,
2, and 3 were successfully initialized.

Message (5) indicates that 4 managers are licensed, but an IP address for manager 4
is not found.
If a number larger than 4 is found, the following the following messages would be issued,
but initialization would continue, and if successful, SNMP messages would be sent.
SNMP: licensed mgrs 6 greater than max number SNMP managers allowed 4
Will use max allowed - 4
60
Aastra – 2808-001
If an error occurs on creating the local socket, a message like the following would be
issued, initialization would be aborted, and no SNMP messages would be sent. Call
processing will still execute as normal.
SNMP: socket open error, errno = 54
If an error occurs on binding the local socket to a local port, a message like the following
would be issued, initialization would be aborted, and no SNMP messages would be sent.
Call processing will still execute as normal.
SNMP: Unable to BIND tb30! errno = 63
Send Error Messages
If an error is returned from a UDP send, a message like the following will be issued, but
no error recovery will be attempted.
SNMP: send error. errno = 50, mgr=10.70.10.56
If not all the message bytes could be accepted by the UDP stack, a message like the
following will be issued, but no error recovery will be attempted.
SNMP: send error. to send=358, sent=63, mgr=10.70.10.56
Aastra - 2808-001
61
62
Aastra – 2808-001
Chapter 7
Sip Registration CIM, Event, EAC Update ARC
OAI CIM, Event, and ARC Messages
Pointspan 5.2 introduces new OAI messages that provide notification when a SPN SIP
device registers with the Pointspan system.
The new OAI CIM message is:

SIP Registration CIM– this CIM is sent when a SIP devices registers with a
Pointspan SPN.
The new OAI Event message is:

SIP Registration Event - this event is sent when a SIP devices registers with a with a
Pointspan SPN.
The new OAI ARC message is:

Update Emergency Calling Party Number – this ARC updates the EAC field of the
Man-Machine FONE command for a specified station. MRM-OK is return to the
application when the disk has been updated successfully. If a disk error occurs when
attempting to update the EAC field, then a new Disk Error MRM is returned.
Configuration

The SIP Station and line must be OAI associated to send the SIP registration CIM

The MM command UGRP/UGP/OCC field will have the OAI channel assigned using
the new OAI toolkit.

The Events report on the OAI Channel defined in command CLCN (Call Center)
OCC field.
Functionality
SIP Registration CIM
The SIP Registration CIM contains the following information:
SIP station registration:

Line ID (OID.LID = 0x01)

Station ID (OID.STAT = 0x2E)

SIP Registration Info (OID.SREG = 0x5D)
SIP trunk registration:

Trunk ID (OID.TTID = 0x03)

Null ID
Aastra - 2808-001
63
Chapter 7, Sip Registration CIM, Event, EAC Update ARC

SIP gateway registration:

SIP Gateway ID (OID.SIPG = 0x5E)

Null ID

Update Emergency Calling Party Number ARC
The “Update Emergency Calling Party Number” ARC contains the following
information:

Station ID (OID.STAT = 0x2E)

Digits ID (OID.DGTS = 0x13)
OAI Requirements
Toolkit 6.9.0 and above, OAI packet log, and switch Oailog utility support for the new
CIM, Event, and ARC specified in this document.
New #defines:
#define OAIK_CIM_SIP_REGISTRATION
60
#define OAIK_ARC_UPDATE_EMERGENCY_CPN
#define OAIKID_SIP_REGISTRATION
100
93
#define OAIKID_SIP_GATEWAY
94
#define OAIK_MRM_DISK_ERROR
92 /* Error on disk read/write */
CIM Message Formats
For Registration from SIP Stations:
------------------------------------------------| Application ID
| Data Byte 1
------------------------------------------------| Application Message ID(MSB)
| Data Byte 2
------------------------------------------------| Application Message ID(LSB)
| Data Byte 3
------------------------------------------------| Type = Call Information = 02
| Data Byte 4
------------------------------------------------| Attr =
60(OMA.SREG)
| Data Byte 5
-------------------------------------------------------------| Line Id – Type = 1
| Data Bytes
------------------------------------------------- as needed
| Station Id – Type = 46
| for each
------------------------------------------------- message
| Registration Info Id – Type = 93
| element
-------------------------------------------------
64
Aastra – 2808-001
OAILOG Display:
SIP Registration CIM 60 (HEX = 3c)
A01-12:(SENT:CIM-SIP Registration) 10ms:26b1dd...Tue Sep 2 14:19:13 2008
LSF:00 LEN:2f AID:03 MNO:b1dd MTY:02 MAT:3c
LSF:002f03b1 dd023c01 00014aa3 002e045b 0b21035d 1c000001 2cc0a806 1ec0a806
06c0a806 1e00085d 1a057305 53504e20 33
Yellow is the format for Registration from SIP stations
Blue is the UGRP/LINE
Pink is the station ID
Green is the SIP Registration Information ID
For Registration from SIP Trunks:
------------------------------------------------| Application ID
| Data Byte 1
| Data Byte 2
| Data Byte 3
| Data Byte 4
------------------------------------------------| Attr =
60(OMA.SREG)
| Data Byte 5
-------------------------------------------------------------| Trunk Id – Type = 1
| Data Bytes
------------------------------------------------- as needed
| Null Id – Type = 127
| for each
------------------------------------------------- message
| element
-------------------------------------------------
For Registration from SIP Gateways:
------------------------------------------------| Application ID
| Data Byte 1
| Data Byte 2
| Data Byte 3
| Data Byte 4
------------------------------------------------| Attr =
60(OMA.SREG)
| Data Byte 5
-------------------------------------------------------------| SIP Gateway Id – Type = 94
| Data Bytes
------------------------------------------------- as needed
| Null Id – Type = 127
| for each
------------------------------------------------- message
| element
-------------------------------------------------
Event Message format for Registration from SIP stations
------------------------------------------------| Application ID
|
|
|
------------------------------------------------| Type = OAI Event = 08
|
Aastra - 2808-001
Data Byte 1
Data Byte 2
Data Byte 3
Data Byte 4
65
------------------------------------------------| Attr = 119(OMA.SPRG)
| Data Byte 5
-------------------------------------------------------------| Unused
| Data Byte 6
------------------------------------------------| Time Stamp (Byte 1)
| Data Byte 7
------------------------------------------------|Time Stamp (Byte 2)
| Data Byte 8
------------------------------------------------| Time Stamp (Byte 3)
| Data Byte 9
------------------------------------------------| Time Stamp (Byte 4)
| Data Byte 10
------------------------------------------------| Message Sequence Number (Byte 1)
| Data Byte 11
| Data Byte 12
| Data Byte 13
| Data Byte 14
------------------------------------------------| System Node Number
| Data Byte 15
------------------------------------------------|Partition Number
| Data Byte 16
------------------------------------------------| Unused
| Data Byte 17
-------------------------------------------------------------| Line Id – Type = 1
| Data Bytes
------------------------------------------------- as needed
| Station Id – Type = 46
| for each
------------------------------------------------- message
| element
-------------------------------------------------
OAILOG Display:
SIP Registration Event 119 (HEX = 77)
A01-05:(SENT:EVNT-SIP REGISTRATION EVENT) 10ms:26b1dd...Tue Sep 2 14:19:13 2008
SEQ:000387ba LSF:00 LEN:40 AID:00 MNO:0000 MTY:08 MAT:77
LSF:00400000 00087700 48bd91b1 000387ba 00000000 31080001 00014aa3 00002e04
5b0b2103 5d1c0000 012cc0a8 061ec0a8 0606c0a8 061e0008 5d1a0573 0553504e 2033
Yellow is the format for Registration from SIP stations
Blue is the UGRP/LINE
Pink is the station ID
Green is the SIP Registration Information ID
ARC Message Format for Update Emergency CPN
------------------------------------------------| Application ID
| Data Byte 1
| Data Byte 2
| Data Byte 3
------------------------------------------------| Type = ARC = 02
| Data Byte 4
------------------------------------------------| Attr = 100(OMA.UEAC)
| Data Byte 5
-------------------------------------------------------------| Station Id – Type = 46
| Data Bytes
------------------------------------------------- as needed
| Digits Id – Type = 19
| for each
------------------------------------------------- message
element
66
Aastra – 2808-001
SIP Registration Information ID
1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
0|I
|I
|E
|E
|
X0|D
|D
|X
|X
|
|T| | | | | | | |L| | | | | | | |P| | | | | | | |1| | | | | | | |
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
4|E
|E
|T
|T
|
X4|X
|X
|I
|I
|
|2| | | | | | | |3| | | | | | | |P| | | | | | | |1| | | | | | | |
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
8|T
|T
|F
|F
|
X8|I
|I
|I
|I
|
|2| | | | | | | |3| | | | | | | |P| | | | | | | |1| | | | | | | |
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
12|F
|F
|C
|C
|
XC|I
|I
|I
|I
|
|2| | | | | | | |3| | | | | | | |P| | | | | | | |1| | | | | | | |
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
16|C
|C
|M
|M
|
X10|I
|I
|A
|A
|
|2| | | | | | | |3| | | | | | | |C| | | | | | | |1| | | | | | | |
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
20|M
|M
|M
|M
|
X14|A
|A
|A
|A
|
|2| | | | | | | |3| | | | | | | |4| | | | | | | |5| | | | | | | |
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
24|T
|T
|
X18|U
|U
|
|L| | | | | | | |N| | | | | | | |
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
FIELD DESCRIPTION:
IDT:
IDL:
EXP:
EX1:
EX2:
EX3:
TIP:
TI1:
TI2:
TI3:
FIP:
FI1:
FI2:
FI3:
CIP:
CI1:
CI2:
CI3:
MAC:
MA1:
MA2:
MA3:
MA4:
MA5:
TUL:
TUN:
Aastra - 2808-001
ID type. OID.SREG = 93 (X'5D')
ID length
Registration Expiration Time in seconds. (1st byte)
Registration Expiration Time in seconds. (2nd byte)
Registration Expiration Time in seconds. (3rd byte)
Registration Expiration Time in seconds. (4th byte)
TO: Domain IP Address, registered IP address (1st byte)
TO: Domain IP Address, registered IP address (2nd byte)
TO: Domain IP Address, registered IP address (3rd byte)
TO: Domain IP Address, registered IP address (4th byte)
FROM: Domain IP Address, registering IP address (1st byte)
FROM: Domain IP Address, registering IP address (2nd byte)
FROM: Domain IP Address, registering IP address (3rd byte)
FROM: Domain IP Address, registering IP address (4th byte)
Contact IP address (1st byte)
Contact IP address (2nd byte)
Contact IP address (3rd byte)
Contact IP address (4th byte)
MAC address of registered device (1st byte)
MAC address of registered device (2nd byte)
MAC address of registered device (3rd byte)
MAC address of registered device (4th byte)
TO: User Name length
TO: User Name (1st character)
67
SIP Gateway ID
1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
0|I
|I
|S
|S
|
X0|D
|D
|G
|G
|
|T| | | | | | | |L| | | | | | | |N| | | | | | | |1| | | | | | | |
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
4|S
|S
|
X4|G
|G
|
|L| | | | | | | |M| | | | | | | |
|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|
FIELD DESCRIPTION:
IDT:
IDL:
SGN:
SG1:
SGL:
SGM:
68
ID type. OID.SIPG = 94 (X'5F')
ID length
SIP Gateway Number
SIP Gateway Number continued
SIP Gateway name length
SIP Gateway Name (1st character)
Aastra – 2808-001
Chapter 8
Pointspan Alarms
SIP Alarms for SPN
Refer to 591-5015-004 Pointspan Alarms Online Help V5.2.
0359
Aastra - 2808-001
Alarm Number
Hex Value
Type
Class
0359
167
MAJ
CARD - SIP
Reason
The SIP application has determined that there is a failure on the
SIP Network. The SIP application is unable to communicate
with the SIP stations.
Result

If the SIP application had been communicating with the SIP
stations and then communications were lost, a
warmstart/switchover to the standby SPN is attempted.

If the SIP application had just been restarted and was never
able to establish communication with any SIP devices, then
the SPN is coldstarted in an attempt to re-establish
communication to the SIP devices.
Suspected Problem
The standby SIP application is reporting that the equalization
process has failed or that the equalization keep-alive poll has
failed. This indicates that some updates from the online SPN
may have been missed.
Data Word 0
SIP application facility number.
Data Word 1
SIP facility state.
Data Word 2
Partition number of the SIP application.
Data Word 3
Network Failure Reason Code:

1 = SIP application restarted and never was able to
communicate with SIP devices.

2 = SIP application was up and communicating and then
lost communication.
Module
R65A.
System Required
Action
Restart the SIP application.
Field Required
Action
Verify the application returns to service and SIP
communications are restored.
69
3700
Alarm Number
Hex Value
Type
Class
3700
E74
MAJ
SIPG
Reason
SIP Gateway registration or authentication failed.
(Refer to reason code below for more information).
Result
SIP registration or authentication was rejected for a SIP Gateway.
This alarm is similar to alarm SIP-3600 used for SIP Stations.
Reason codes are coordinated between the alarms.
Data Word 0
For Reason 1, 2, 16, or 17:
SPN facility.
All other reason codes:
SIP Gateway facility.
Data Word 1
70
Reason Code (decimal value):
1
(Reserved for alarm SIP-3600).
2
SIP Gateway identified in SIP Authentication Name
does not exist on the SPN Partition.
3
4
5
Reported SIP authentication password does not match
the password defined for the SIP Gateway.
6
Unsupported SIP Version - SIP version not SIP 2.0 or
greater.
7
Invalid Registration Address-of-Record ("To:").
8
Invalid Registering Address-of-Record ("From:").
9
Invalid Contact Information.
10
Expiration Interval Too Short.
11
12
Invalid Registration ID received in SIP Registration
request message.
13
Q07 Disk Read of SIP Gateway password failed.
Aastra – 2808-001
Alarm Number
Data Word 2
Hex Value
Type
Class
14
Existing SIP Registration expired and did not reregister within 10 minutes from the time of expiration -for a single SIP Gateway.
15
16
SIP authentication domain is incorrect (does not match
SPN IP Address).
17
18
SIP Gateway implicit registration - Q07 disk read
failed.
19
SIP Gateway implicit registration - SPN reported
failure.
20
SIP Gateway implicit registration - SPN did not
respond to request.
21
Explicit Registration received from SIP Gateway when
SIP Gateway setup for Implicit Registration.
For Reason 18, 20:
Unused (0).
For Reason 19:
SIP response code ($SR.) received from SPN.
SIP Gateway IP address (where SIP registration or authentication
was requested).
Data Word 3
Action Taken:
0
Not Applicable (Reason=14).
1
SIP registration or authentication allowed to continue.
2
SIP registration or authentication rejected.
3
SIP Gateway implicit SIP registration will periodically
be retried, until the implicit registration completes
successfully.
Module
CG3A, CG5A. - E.SGRGF.
System Required
Action
SIP Registration or Authentication Rejected (if indicated by action
taken).
Field Required
Action
Action to take based on Reason Code:
Code
1
Aastra - 2808-001
Action
71
Alarm Number
72
Hex Value
Type
Class
2
Correct the SIP authentication name, or change the
SIP Gateway proxy to that of the correct SPN
partition
3
4
5
Correct the SIP authentication password in the SIP
Gateway, or correct the password defined for the SIP
Gateway.
6
Check SIP Gateway software version.
7
Check SIP Gateway configuration.
8
9
10
Increase SIP Gateway registration expires interval to
a value more than the minimum (as defined for the
SPN partition).
11
12
Report to CSC (software support).
13
If occurs repeatedly, report to CSC (Software
Support).
14

Verify SIP Gateway is on the network.

Check network path.
15
16
Correct the SIP authentication domain.
17
18
If occurs repeatedly, report to CSC.
19
20
21
Either change Pointspan configuration for SIP
Gateway to use Explicit SIP Registration, or change
SIP Gateway configuration to disable SIP
Registration.
Aastra – 2808-001
3703
Alarm 3740 was renamed to 3703.
Alarm Number
Hex Value
Type
Class
3703
E77
INF
SIPG
Reason
SIP trunk dialog (PM6) chain error.
An error was found during validation / usage of the SIP Trunk
Dialog (PM6 entry) Chain for a SIP Gateway.
Result
SIP trunk dialog chain rebuilt for SIP Gateway.
Data Word 0
SIP Gateway Facility.
Data Word 1
Aastra - 2808-001
Error Code (decimal value):
1
Chain has infinite loop.
11
Head entry contains an invalid PM6 entry #.
12
Head entry but no tail entry.
13
Head PM6 entry not allocated.
14
Head PM6 entry not assigned to SIP trunk.
15
Head PM6 entry not assigned to SIP trunk on this SIP
Gateway.
16
Head PM6 entry has invalid backward link.
17
Head PM6 entry has invalid forward link.
21
Tail entry contains an invalid PM6 entry #.
22
Tail entry but no head entry.
23
Tail PM6 entry not allocated.
24
Tail PM6 entry not assigned to SIP trunk.
25
Tail PM6 entry not assigned to SIP trunk on this SIP
Gateway.
26
Tail PM6 entry has invalid backward link.
27
Tail PM6 entry has invalid forward link.
31
(Unused).
32
(Unused).
33
PM6 entry (on chain) not allocated.
34
PM6 entry (on chain) not assigned to SIP trunk.
73
Alarm Number
Data Word 2
Hex Value
Type
Class
35
PM6 entry (on chain) not assigned to SIP trunk on this
SIP Gateway.
36
PM6 entry (on chain) has invalid backward link.
37
PM6 entry (on chain) has invalid forward link.
Contents based on error code:
Error codes 01, 11, 12, 13, 14, 15, 16, 17, 21, 22, 23, 24, 25:
Head SIP Trunk Dialog (PM6 entry) for SIP Gateway.
Error codes 26, 27:
Tail SIP Trunk Dialog (PM6 entry) for SIP Gateway.
Error codes 33, 34, 35:
Previous PM6 Entry (on chain).
Error code 36, 37:
PM6 Entry (on chain).
Data Word 3
Contents based on error code:
Error codes 01, 11, 12, 13, 14, 15, 21, 22, 23, 24, 25:
Tail SIP Trunk Dialog (PM6 entry) for SIP Gateway.
Error codes 33, 34, 35:
Invalid PM6 Entry.
Error codes 16, 17, 26, 27, 36, 37:
Invalid forward or backward link PM6 Entry.
74
Module
CG1A - E.STDCE.
System Required
Action
None.
Field Required
Action
If alarm occurs several times, report to CSC.
Aastra – 2808-001
3704
Alarm Number
Hex Value
Type
Class
3704
E78
MIN
SIPG
Reason
On a SIP Gateway, an ISDN PRI/T1 Span or Analog Trunk to
the Public Network is Out-of-Service or has failed.
This may be a temporary or permanent condition. This alarm is
generated every time an outbound SIP trunk call is attempted
and fails. The alarm is throttled to not be reported any more
than once every 4 minutes for any particular Pointspan Trunk
Group.
If the condition changes and either an inbound or outbound call
is successful across the SIP Trunk Group, alarm SIPG-3705 is
generated to indicate the condition no longer exists (the trunks
are back in-service).
Result
Aastra - 2808-001

Outbound call resubmitted to Route Guide processing in an
attempt to select an alternative

trunk (not within this SIP Trunk Group) for the outbound
call.
Data Word 0
Data Word 1
Pointspan SIP Trunk Group.
Data Word 2
SIP Request Id (for outbound call which received the indication
the trunks are out-of-service).
Data Word 3
SIP Response Code (received from SIP Gateway, indicating the
trunks are out-of-service).
Module
C21A - E.SGTOS.
System Required
Action
None.
Field Required
Action
Consult status on SIP Gateway to determine why the trunk(s) to
the Public Network are out-of-service/failed. Take appropriate
action to bring the trunks back in-service.
75
3705
Alarm Number
Hex Value
Type
Class
3705
E79
INF
SIPG
Reason
On a SIP Gateway, an ISDN PRI/T1 Span or Analog Trunk to
the Public Network is now back In-Service.
Alarm SIPG-3704 had been previously generated because a SIP
Gateway reported trunks out-of-service or failed for an
outbound call using this Pointspan SIP Trunk Group.
Calls are now being processed normally for this SIP Trunk
Group, indicating the out-of-service condition no longer exists.
76
Result
Calls now processing normally across the Pointspan SIP Trunk
Group.
Data Word 0
Data Word 1
SIP Trunk Group.
Data Word 2
Unused (0).
Data Word 3
Unused (0).
Module
C21A - E.SGTIS.
System Required
Action
None.
Field Required
Action
None.
Aastra – 2808-001
3706
Alarm Number
Hex Value
Type
Class
3706
E7A
MIN
SIPG
Reason
An outbound call routed through a SIP Gateway was rejected by
the SIP Gateway due to a failure.
The failure may be due to:

Pointspan sending an incorrect Destination Number to the
gateway.

SIP Gateway improperly setup, such that there is no route to
the destination, etc.

Rejection of the call by the public network trunk to which
the SIP Gateway routed the call.
This alarm is generated every time an outbound SIP trunk call is
attempted and fails.
The alarm is throttled to not be reported any more than once
every 4 minutes for any particular Pointspan Trunk Group.
Aastra - 2808-001
Result
Reorder played to caller due to the failed outbound call.
Data Word 0
Data Word 1
SIP Trunk Group.
Data Word 2
SIP Request Id (for outbound call which received failure
notification from the SIP Gateway).
Data Word 3
SIP Response Code (received from SIP Gateway indicating the
failure of the call).
Module
C21A - E.SGTCF
System Required
Action
None.
Field Required
Action
Check the following possible issues:

Verify the destination number sent to the SIP Gateway by
Pointspan is correct.

Verify the Number Manipulation and Routing tables on the
SIP Gateway are correct.

Verify the called number is valid.
77
3710
Alarm Number
Hex Value
Type
Class
3710
E7E
MAJ
SIPG
Reason
SIP gateway not responding.
(Refer to Reason Code below for more information.)
Result
Refer to Action Taken below. Active calls on the SIP Gateway
may terminate.
Data Word 0
Data Word 1
SPN Partition Number (where the SIP Gateway resides).
Data Word 2
SIP Gateway IP Address.
Data Word 3
Reason Code (High Order half of Data Word 3):
1
SIP Registration Expired.
2
(Unused - Reserved).
3
Service check of SIP Gateway received no response.
Action Taken (Low Order half of Data Word 3):
0
No action taken.
5

No calls on the SIP Gateway are terminated, except
those calls that cannot be terminated by the
connected party.

Existing SIP Gateway registration is terminated.

SIP trunks associated with the SIP Gateway are
placed Maintenance Out-of-Service (MOS),
pending a subsequent successful SIP Gateway
registration.

Calls in-transition on the SIP Gateway are
terminated.

No active calls on the SIP Gateway are terminated,
except those calls that cannot be terminated by the
connected party.


SIP trunks associated with the SIP Gateway are
placed Maintenance Out-of-Service (MOS),
pending a subsequent successful SIP Gateway
registration.
6
78
Aastra – 2808-001
Alarm Number
Hex Value
7
Type
Class

All calls on the SIP Gateway (including active
calls) are terminated.


SIP Trunks associated with SIP Gateway are placed
Maintenance Out-of-Service (MOS), pending a
subsequent successful SIP Gateway registration.
Module
CH2A - E.SGSUP.
System Required
Action
None.
Field Required
Action

Verify SIP Gateway connection to the network.

Verify SIP Gateway is properly operating.
Alarm Number
Hex Value
Type
Class
3720
E88
MAJ
SIPG
Reason
SIP Gateway Start-Up (Power-Up).
3720
This occurs when the SIP Gateway power cycles, or is otherwise
re-started.
(Refer to Reason Code below for more information).
Result
Active calls on the SIP Gateway may have been terminated.
Refer to Action Taken below.
Data Word 0
Data Word 1
SPN Partition Number (where the SIP Gateway resides).
Data Word 2
Data Word 3
Reason Code (High Order half of Data Word 3):
1
SIP Gateway Start-Up as Reported by Power-Up
Notification.
2
SIP Gateway Start-Up as Detected by New SIP
Registration.
Action Taken (Low Order half of Data Word 3):
Aastra - 2808-001
0
No action taken.
1
those calls that cannot be terminated by the connected
party.
79
Alarm Number
Hex Value
2
Class

terminated.

connected party.
3
All calls on the SIP Gateway (including active calls) are
terminated.
5

those calls that cannot be terminated by the
connected party.


SIP Trunks associated with SIP Gateway are placed

terminated.

connected party.


SIP trunks associated with SIP Gateway are placed

All calls on the SIP Gateway (including active
calls) are terminated.


SIP trunks associated with SIP Gateway are placed
6
7
80
Type
Module
CH2A - E.SGSUP.
System Required
Action
None.
Field Required
Action
None.
Aastra – 2808-001
3730
Alarm Number
Hex Value
Type
Class
3730
E92
MAJ
SIPG
Reason
SIP Gateway Registration with different contact (than existing,
active SIP Registration)
SIP Gateway may register with a different contact when:
Result

SIP Gateway is restarted/powered-up and DHCP assigns a
different IP address (this is not a problem).

More than one SIP Gateway is configured with the SAME
Authentication Name and Password (this configuration
problem must be corrected).
The following actions are taken:

All calls on the SIP Gateway are terminated.

Existing SIP Registration terminated for SIP Gateway.

New SIP Registration completed with new Contact IP
Address.
Data Word 0
Data Word 1
SPN Partition Number (where SIP Gateway resides).
Data Word 2
SIP Gateway IP Address (Existing).
(Contact IP Address from existing SIP Registration.)
Data Word 3
SIP Gateway IP Address (New).
(Contact IP Address from new SIP Registration.)
Module
CH2A - E.SGCON.
System Required
Action
None.
Field Required
Action
If alarm occurs several times:
Alarm Number
Hex Value
Type
Class
3790
ECE
INF
SIPG
Reason
SIP Gateway Active.
Result
SIP Gateway now available to place and receive calls.
Verify the same Authentication Name and Password are NOT
configured on more than one SIP Gateway.
3790
Aastra - 2808-001
81
Alarm Number
Hex Value
Type
Class
Data Word 0
Data Word 1
SPN Partition Number (where SIP Gateway resides).
Data Word 2
Data Word 3
SIP Gateway Number.
Module
CH2A - E.SGACT.
System Required
Action
None.
Field Required
Action
None.
Modified Alarms
3600
Alarm Number
Hex Value
Type
Class
3600
E10
MIN
SIP
Reason
SIP Station registration or authentication failed.
Refer to the reason codes in Data Word 1 below for more
information.
Result
SIP registration or authentication was rejected for a SIP
Station/Voice Line pair.
This alarm is similar to alarm SIPG-3700 used for SIP Gateways.
Reason codes are coordinated between the alarms.
Data Word 0
If reason = 1, 2, 15, 16, or 17:
SPN facility.
SIP Station Logical Port Facility.
Data Word 1
82
Reason Code (decimal value):
1
SIP Authentication Name has an incorrect format or
does not exist. The SIP Device (SIP Station or SIP
Gateway) could not be determined.
2
SIP Station identified in SIP Authentication Name
does not exist on the SPN Partition.
3
SIP Station is NOT reporting a MAC Address (which
is needed to match against the MAC Address defined
for the SIP Station).
Aastra – 2808-001
Alarm Number
Hex Value
Type
Class
4
MAC Address reported by SIP Station does not match
the MAC Address defined for the SIP Station.
5
Reported SIP Authentication Password does not
match the password defined for the
SIP Station.
6
Unsupported SIP Version - SIP version not SIP 2.0 or
greater.
7
Invalid registration address-of-record ("To:").
8
Invalid registering address-of-record ("From:").
9
Invalid contact information.
10
Expires interval too short.
11
SIP Station (from Authentication Name) and Voice
Line (from Registration Address-of-Record) not
related.
12
Invalid Registration ID received in SIP Registration
Request Message.
13
Q07 disk read of SIP station password failed.
14
Existing SIP registration expired and did not reregister within 10 minutes from the time of expiration
-- for a single SIP Station.
15
Existing SIP registration expired and did not reregister within 10 minutes from the time of expiration
-- for more than 3 SIP Stations within the 10-minute
period.
16
SIP authentication domain is incorrect (does not
match SPN IP Address).
17
SPN password request from ECS failed (Timeout).
This reason code applies to SPN password requests
for both SIP Stations and SIP Gateways.
Data Word 2
18
(Reserved for alarm SIPG-3700).
19
20
21
If reason = 15:
Number of SIP Stations where SIP registration expired within 10minute period.
Aastra - 2808-001
83
Alarm Number
Hex Value
Type
Class
SIP Device IP Address (from which SIP Registration or
Authentication was requested).
Data Word 3
Module
Field Required
Action
84
Action Taken:
0
Not applicable (Reason=14 or 15).
1
SIP registration or authentication allowed to continue
(not blocked due to MAC address validation failure).
2
SIP registration or authentication rejected.
CG3A, CG5A, E.SREGF.
Action to take based on Reason Code:
Code
Action
1
Correct the SIP authentication name.
2
Correct the SIP authentication name, or change SIP
Station proxy to that of the correct SPN partition.
3
Change the SIP Station to enable reporting of the MAC
Address to the SPN (only possible for Aastra phones).
4

If the defined SIP Station MAC Address is
incorrect, change it to the proper MAC Address.

If the SIP Station is attempting to register to an
incorrect Pointspan logical port (as identified in the
SIP authentication name), correct the SIP
authentication name.
5
Correct the SIP authentication password in the SIP
Station or correct the password defined for the SIP
Station.
6
Check SIP Station software version.
7
Check SIP Station configuration.
8
Check SIP Station configuration.
9
Check SIP station configuration.
10
Increase SIP Station registration expires interval to a
value more than the minimum (as defined for the SPN
partition).
11
Check SIP station configuration.
12
Report to CSC (software support.)
13
14
Verify SIP Station is plugged into the network. Check
network path.
Aastra – 2808-001
Alarm Number
Aastra - 2808-001
Hex Value
Type
Class
15
Check network path to SIP Stations.
16
Correct the SIP authentication domain.
17
18
19
20
21
85
86
Aastra – 2808-001

Pointspan 5.2 Features and Enhancements

Transcription

Similar documents

a flyer on making the transition to IP

Passerelle GSM - voipsolutions.gr

GXP2160 - Allnet.Italia Store

take a sip every time - Roller Derby Belgium

Quick Start Guide P1.ai

KamailioWorld 2014

Kamailio World

Designing and Building Our Net-Zero Home

KX-NS1000/700 SIP Trunk Configuration Guide

OpenSIPS as an IP-PBX replacement in a multi