General

1.  AG

Product Name: winTrunk

Codec / Frame Length: G.711a / 20 ms

Fax: T.38 Minutes ¹⁾

Registration of SIP Accounts: The communications server registers using a special SIP account that is completely independent of the assigned number range.

ALG Function: The Winet platform communicates directly with the private IP addresses of the Aastra Communication Server and the IP phones. Therefore, the ALG function must not be enabled on either the NAT router or the Aastra Communication Server.

1) T.38 is only available for phone numbers that have been previously registered with Winet.

1. 400

Aastra Communication Server: Aastra 415, Aastra 430, Aastra 470 Release 3.0 SP1 HF1

Software Version: 8444a1

Voice Gateways: EIP or Standard Media Switch

Information on Aastra Mobility Solutions

The following call scenarios were tested:

• A cell phone calls an external subscriber via AMC 3 «Call-Through,» places the call on hold using the AMC 3 application, and transfers it to an internal user with an IP endpoint.
• An external caller uses an Aastra 400 to call an internal user on a mobile phone. The mobile phone places this call on hold using the AMC 3 application and transfers the external caller to an internal user with an IP endpoint.
• An internal user with an IP-based device calls an internal user with a cell phone. The cell phone places this connection on hold using the AMC 3 application and transfers the caller to an internal user with an AD2 device.
• An external caller uses an Aastra 400 to call an internal user on a cell phone (in One Number 1:n).
• An internal user with an IP device initiates a Fast Take to an internal user with a cell phone, whose line is currently busy.
• A cell phone uses the AMC 3 application to initiate a "Fast Take" to an occupied internal user with an IP device.
• One cell phone calls another cell phone. The second cell phone places this call on hold using the AMC 3 application and transfers the caller to an internal user with an IP-based device.
• A cell phone (without an available data connection) calls an external subscriber using the AMC 3 application.
• An external caller dials a cell phone (without an available data channel).

Notes on the AMC 3 Solution:

• All tests were conducted using a mobile phone (Android operating system v4.3) and the AMC software versions AMCC 10684.16.5 and AMC 4-Client 4.0.2 Build 3527.
• The «winTrunk» must have the «CLIP no screening» option enabled so that the CLIP number of the calling A subscriber is displayed on the mobile phone being called.
• In the call scenario «An external caller uses an Aastra 400 to call an internal user on a cell phone,» the cell phone displays always the CLIP number of the calling external A subscriber is presented.

1. (Controller)

The following call scenarios¹⁾ The following were tested:

• A GSM cell phone calls an external subscriber using a GSM integration number, places the call on hold, and transfers it to an internal user with an IP-based terminal.
• An external caller uses an Aastra 400 to call an internal user with a GSM device. The GSM cell phone places the call on hold and transfers it to an internal user with an IP device.
• An internal user with an IP device calls an internal user with a GSM device. The GSM cell phone places this connection on hold and transfers the caller to an internal user with an AD2 device.
• An external caller uses an Aastra 400 to call an internal user with a GSM device (in One Number 1:n).
• An internal user with an IP device initiates a Fast Take to an internal user with a GSM device, whose GSM cell phone is currently busy.
• A GSM cell phone performs a "Fast Take" on an occupied internal user with an IP terminal.

Notes on GSM Integration:

• The «winTrunk» must have the «CLIP no screening» option enabled so that the CLIP number of the calling A subscriber is displayed on the called GSM cell phone.
• With the Aastra 400, it is possible to transmit the CLIP number of the Aastra 400«s GSM terminal (B-subscriber) to the called GSM mobile phone instead of the CLIP number of the calling external A-subscriber (e.g., multi-tenant functionality). If this is desired, the parameter »Send incoming CLIP for PBX-to-PBX connections« must be set to »No« in the corresponding SIP bundle (AMS CM_3.1.5 bundle, »CLIP” tab).
• Conferences with two external participants initiated by an AMC 3 user are currently not possible.

1) This also applies to an Aastra Mobile Client (AMC 2.0) installed on a GSM cell phone.

1. Restrictions

• To enable all call scenarios in conjunction with «winTrunk,» the RTP data stream must always be routed through the communication server (known as «indirect switching»; AMS_CM_3.2.4, parameter «Route RTP data stream via communication server» set to «Yes»). When planning your project, please note that «indirect switching» may require more VoIP resources in the Aastra 400.

Important: No tests were conducted using «Direct Switching,» so «Direct Switching» in combination with «winTrunk» not Approved.

• Winet uses domain names for the SIP registrar and the SIP proxy. Please configure at least one IP address of a valid DNS server (AMS_CM_2.2.1) in the Aastra 400.
• If the Communication Server does not have any ISDN trunk lines, please disable clock synchronization on all ISDN trunk ports (if present) and then restart the Communication Server. Next, verify that the «Sync Status» parameter displays the status «Idle» (AMS CM_3.2.1.1, «Clock Reference» tab).
• To ensure that the Communication Server's clock remains accurate even when ISDN trunk lines are unavailable, we recommend using an NTP time server (AMS CM_2.3.3.5).

Example: europe.pool.ntp.org

• For call forwarding via SIP trunk – SIP trunk, we recommend using the SIP Diversion header «non-recursing» (AMS_CM_3.2.4) so that the calling party’s number (A-number) is displayed to the recipient. For SIP trunk call forwarding to SIP trunk (within the Aastra 400) without a SIP Diversion header, the external recipient of the forwarded call will always see the calling party’s number (B number) as the CLIP.
• To ensure that outgoing CLIP transmission works as well as possible, we recommend that each user leave the «CLIP automatically» setting set to «Yes» (AMS CM_4.1 users).
• «winTrunk» supports the «CLIP no screening» feature. This feature allows Aastra 400 users to transmit CLIP numbers on outgoing calls that do not belong to the assigned number range (e.g., 0800 xxx xxx), or, when using one of the two Aastra mobility solutions, the phone numbers of external callers can also be transmitted to the called mobile phones in certain call scenarios.
• When transferring external or internal calls without In rare cases, the A-participant may not hear a dial tone during pre-registration.

Configuring the Aastra 400 Communication System

• These configuration instructions describe only the SIP-specific configurations required to operate the Aastra 400 with «winTrunk» from Winet Network Solutions AG.

For information on required hardware, licenses, and other configuration options, please refer to the relevant system manuals.

• The screenshots are based on AMS 3.0.22c and software version 8444a1 of the Aastra 400 Release 3.0 SP1 HF1.
• Please change only the parameters that are specifically marked; leave the rest in their default settings as much as possible, as shown in the screenshots below.

• configure

Aastra 400 WebAdmin allows you to import the SIP provider settings specified in «CM_3.2.4 SIP Provider» using an XML file. This XML file is available for download in the KnowledgeBase under «TI 1537.».

AMS CM_3.2.4 SIP Provider/Account

2)

3)

4)

5)

1. «Set the »From field for CLIR« to »Retrieve from SIP account (RFC 3323).".
2. «Set »Music While Waiting« to »Yes.".
3. «Set »Music While Waiting: Signaling« to »No Signaling (no media updates).".
4. «Set »Send redirection information« to »Yes, with Diversion header (non-recursing).".
5. Set the «Preferred Codec» parameter to «G.711a.».
6. Enter «sbc.winet.ch» as the registrar and proxy.
7. Set the preferred registration interval to 120 seconds.
8. «Set »Enable keep-alive« to »Yes"
9. «Set »Route RTP data stream via communication server« to »Yes.".
10. Specify the desired bundle number for Winet.
11. «Set »Provider Authentication« to »With an Account"

• configure

AMS CM_3.1.5 Bundle, «Bundle» tab»

1. Define the extension plan for the «winTrunk» phone numbers.

If you need multiple extension plans (e.g., for a mixed «winTrunk»/ISDN setup), define the extension plan in the SIP bundle before opening the SIP accounts. This should not must be identical to the extension plan for the ISDN bundle!

AMS CM_3.1.5 Bundle, «Features» tab»

• If the Diversion header is enabled in the SIP provider configuration (AMS CM_3.2.4), the «Send redirection information» parameter must be set to «Yes» here.

If the Diversion header is not enabled in the SIP provider configuration, the «Send redirection information» parameter must be set to «No» here.

AMS CM_3.1.5 Bundle, «CLIP» tab»

• Define a CLIP number here for the following cases:

3)

If an internal user (with «Automatic CLIP = Yes») does not have an assigned extension number, the CLIP number configured here will be sent along with the call.

• Outgoing calls made using the line buttons on the switchboard units include the CLIP number configured here (if the system setting is AMS CM_2.3.2).

• «Set »Transit CLIP Format« to »Unknown with national prefix.".

• configure

AMS CM_3.1.6 Routes

Add the previously configured SIP bundle to the desired route.

• configure

AMS CM_3.2.4 SIP Provider/Account

• Click in the empty field on the «SIP Account» tab and select «Add.».

1. In the «SIP-ID» field, enter the username you received from Winet.

• The "Extension Number" field remains blank.

• Enter the information you received from Winet in the «Username» and «Password» fields.

• The «Registration Required» parameter must be set to «Yes.».

• The «Default Account» parameter must be set to «Yes.».

• The «From Field Type» is «System CLIP.».

Note:

With «winTrunk,» the communications server registers using a special SIP account that is completely independent of the assigned number range.

• configure

AMS CM_3.1.3 Extension Plans

1. Use the «New Numbers» button to set up the entire SIP phone number block in the format 0xxxxxxxxx.

AMS CM_3.1.3 Extension Plans, «ARV Destinations» tab»

• Now configure the desired ARV destination for each extension number.

• Fax port

AMS CM_4.2 Terminal Data, «Analog Settings» tab»

1) Set the «Fax Device» parameter to «Multifunction Device (Voice/T.38).».

When using T.38, please note that you must use the appropriate DSP configuration with «FoIP» (AMS CM_2.1.3) or an EIP card. For information on required hardware, licenses, and system limits, please refer to the relevant system manuals.