Configuration

This section defines the normal configuration data needed to be sent to the IP-POTs card for proper operation.

Each Card needs to be configured for service. This can be templated in most cases: 
 

Voice VLAN - The voice VLAN can be configured on each Tellabs 1000 IP-POTS card.  All voice traffic coming from the card is tagged.  Up to 154 cards (7 expansion shelves * 22 slots/shelf) can be placed into a fully equipped terminal.  Each card on the system has a single IP address.  Since 154 cards fit nicely within a class C subnet (255.255.255.0 mask), it is anticipated that the same VLAN will be utilized for the entire Terminal.  

TConfig Username - The username used to log into the EMS to download voice configuration data.  The system auto-generates a unique username unless overridden.

TConfig Password - The password used to log into the EMS to download voice configuration data.

Equipment Settings Profile: This is assigned at the card granularity.  It is typically static based on operator conventions and is likely the same for the whole network.   It configures the protocol (udp/tcp/tls), Sip Timers, SIP port numbers, and how often to refresh the configuration data (default is every 24 hours). 

Phone Number/AOR - Since this is a VoIP line and the IPOTS needs to register with the Softswitch, the phone number of the subscriber is needed for registration.   This is needed for each subscriber line.  This is an AOR in SIP terms or Address of Record.  The AOR is typically of the form: sip:+2145551212@serviceprovider.com.  This is a free-form text field of max length 32.

Softswitch Username - The username to be used when the IP-POTS registers a voice line or is challenged by the switch on making a call.  The username/password is needed so that the voice line can be logged into the switch.  It varies by operator whether this is different per voice line, or the same on all voice lines.  This is a freeform text string of max length 32.  Username/password is only used if the port is challenged by the switch.

Softswitch Password - The password used for the IP-POTS card to log into the Softswitch when registering or making calls.  This is a freeform text string of max length 32.

There are also currently two profiles which are configured and assigned at the line level.  These profiles are typically set up once within Panorama INM and then assigned to the cards either from the GUI or via an external OSS.  The system is configured by giving the name of the profile to assign.

Services Profile - The services profile for the most part defines how to connect to the Softswitch.  It can either be set up to explicitly connect to a given SBC, or alternatively use a hostname/FQDN, but have DNS return the correct entry for this locality.  The services profile is assigned per voice line.  For a given terminal, the expectation is that the same profile would be assigned to every line as they would likely all home into the same Softswitch.  If you use the DNS approach, it could be the same across the network.

Call Features Profile - This profile defines the dial plan (usually the same for all customers) and the calling features allowed.  Usually all are enabled as many of these features can be controlled on the switch as well.

Admin State - Set to enabled, or disabled, enables the line to go into service and attempt registration with the switch, or disables, which causes it to de-register the line, go into an idle state, and deny battery on the line. 

Voice Line Status - The voice line status is also available on the EMS.  

AdminStatus - Admin Status is repeated here as an convenience so that it is clear whether the line is enabled.

Registration State - Shows the current registration state whether unconfigured, registered, authentication failure or registration timeout.

Call State - Whether the line is offhook or onhook currently.

Operational State - Reflects the current Admin State.

Softswitch Testing 

The IP POTs card is built on a stack that has a long history of deployment with many switches.  Tellabs has extensive experience interfacing with many Softswitches.   To ensure 100% compatibility Tellabs typically will run a regression test with the customer's switch, run testing of all switch features, and address any issues found.  This can be performed onsite or via remote access to the Softswitch.  The test typically only takes about two weeks.

The stack has been tested against the following switches: 

• Aastra 400
• Alcatel OXE
• Alcatel HPSS 3.0.3
• Asterisk
• Avaya AS5300
• Avaya CM6
• Avaya Aura 7.1
• Broadsoft
• Cisco CUCM R10.x and R11.x
• Genband Experius 11.2
• Metaswitch (various releases)
• Mitel 400/3300 
• NEC Univerge Rel 8.6
• NEC 8500
• Nortel CS1500
• Nortel CS2K
• Redcom Slice / HDX