IP DECT: Phones can not place outgoing calls
Document Id: KB01018099
Last Modified Date: 07/24/2007
Author: dsenashenko
Products: IP DECT
Version-Release
IP DECT 1.1.3
CM 4.0.0-730.5
Details
CM update 13566
IP DECT Base Station Versions:
version of initial booter : 2.0.12
Version of booter 1 : 3.2.8
Version of booter 2 : 3.2.8
Hardware Revision : 51
Description (Problem Clarification)
IP DECT Phones can not place outgoing calls.
Cause
It is issue of wrong Avaya Communication Manager (ACM) settings.
Problem Fix/Workaround/Solution
Need to set right settings
The main things are into Xmobile station form 'Mapping Mode - both'
Configuration set - blank
Into Signaling group - TSC - number of trunk group
Into trunk - TSC trunk member - 1
link to the documentation:
Resolution Plan
User needs to set right settings to ACM
After implementation of right settings, issue is fixed
IP DECT: Unable to make outgoing calls
Document Id: KB01020438
Last Modified Date: 07/04/2007
Author: dsenashenko
Products: IP DECT
Version-Release
S8300-013-01.3.640.2
Details
S8300 and some Media Gateway (MG) and IP DECT
IP DECT 1.1.3
Description (Problem Clarification)
IP DECT hanging off S8300. DECT stopped to terminate outgoing calls, but can receive incoming calls.
Cause
Wrong configuration of IP DECT trunk
Inserted '0' to Calling Number Insert field
Finally Communication Manager (CM) received Calling Party Number (CPN) and '0' plus extension of DECT. The mapping between CM DECT forms and DECT extensions did not work, and CM could not terminate outgoing from DECT calls
Problem Fix/Workaround/Solution
Need to clear '0'
Need to set right settings absolutely the same as it is said in Avaya Official Documents
Resolution Plan
Clear '0'
Set right settings
Communication Manager: Xmobile (DECT) station not able to dial out, not even receiving dial tone on outgoing call after upgrade from CM2.2 to CM 3.1.4
Document Id: KB01021080
Last Modified Date: 09/12/2007
Author: chhangani
Products: Communication Manager, DECT, S8700 Media Server
Version-Release
Avaya -- Proprietary and Confidential. Internal Distribution Only. Use pursuant to Avaya policy
S8700-013-01.4.642.1 + 14049
DECT R2
Details
Avaya -- Proprietary and Confidential. Internal Distribution Only. Use pursuant to Avaya policy
init@server> swversion
Operating system: Linux 2.6.11-AV18 i686 i686
Built: Mar 9 15:26 2007
Contains: 01.4.642.1
Reports as: R013x.01.4.642.1
Release String: S8700-013-01.4.642.1
UPDATES:
01.4.642.1-13743 unpacked hot patch 13743 for 01.4.642.1
01.4.642.1-14049 activated hot Incremental Build for cm3-642.1
Description (Problem Clarification)
Avaya -- Proprietary and Confidential. Internal Distribution Only. Use pursuant to Avaya policy
Customer has several DECT problems, after they upgrade CM from 2.2 to CM3.1.3 and then to CM 3.1.4
Issue:
- Can receive calls from internal extensions or external numbers
- CANNOT make any outgoing calls. No dial tone, when trying to call any number (internally or externally)
Cause
Avaya -- Proprietary and Confidential. Internal Distribution Only. Use pursuant to Avaya policy
Configuration issue. Some fields have changed in CM3.1.4. related to DECT phones.
Problem Fix/Workaround/Solution
Avaya -- Proprietary and Confidential. Internal Distribution Only. Use pursuant to Avaya policy
-After upgrade a new field "Calling Number Verification" was added into "change xmobile configuration-set 10" with default value set to "y". For xmobile stations which have been assigned config-set 10 this is a wrong setting. Need to set it to "n".
-Also by default after upgrade "change station" form with type "Xmobile" has "Configuration set " field - set to blank. But this was not true in our case the DECT stations are showing up with config-set of 10. If this is not the case need to put correct number of "configuration set" where "Calling Number Verification" is set to "n" to all the DECT phones.
Resolution Plan
Avaya -- Proprietary and Confidential. Internal Distribution Only. Use pursuant to Avaya policy
From the Docs : Important:
The default value y restricts incoming calls to "network provided" or "user provided verified and passed" calling numbers. When the switch is part of a private network and you are not screening calling numbers, change the field to n.
change xmobile configuration-set 10 Page 1 of 1
CONFIGURATION SET: 10
Configuration Set Description: Dect
Calling Number Style: pbx
CDR for Origination: phone-number
CDR for Calls to EC500 Destination? y
Fast Connect on Origination? y
Post Connect Dialing Options: both
Cellular Voice Mail Detection: none
Barge-in Tone? n
Calling Number Verification? n <-------------------------------------this field was set to yes earlier
Identity When Bridging: principal
display station 3831 Page 1 of 3
STATION
Command: disp sta 3831
Extension: 3831 Lock Messages? n BCC: 0
Type: XMOBILE Security Code: TN: 1
Coverage Path 1: COR: 13
Name: CCC Coverage Path 2: COS: 1
Hunt-to Station:
STATION OPTIONS
XMOBILE Type: DECT Message Lamp Ext: 3831
Display Module? y Message Waiting Type: ICON
Display Language: english Length of Display: 12x3
Mobility Trunk Group: 120 Calls Allowed: all
Configuration Set: 10 <-------------------------------------every station has a config-set number.
DECT, CM: Outgoing calls receive busy tone
Document Id: KB01021109
Last Modified Date: 08/23/2007
Author: dsenashenko
Products: DECT, Communication Manager
Expert System?
Avaya -- Proprietary and Confidential. Internal Distribution Only. Use pursuant to Avaya policy
DEFAULT
Version-Release
ACM 3.1.2 - 12866
DECT R2 firmware 44100204
Details
There is a main server which has Port Network (PN) installed with DECT R2, and an Enterprise Survivable Server (ESS) with the same software and patch.
Description (Problem Clarification)
When PN goes to ESS, all the outgoing calls to DECT receive the busy tone. The outgoing calls from DECT work normally.
Cause
ESS had license without Xmobility
After installing DECT user forgot to download a new license to ESS
Problem Fix/Workaround/Solution
This issue can be resolved by installing a new license on ESS.
Resolution Plan
Install a new licence on ESS.
-----------------------------------------------------
Extension: 164 Lock Messages? n BCC: 0
Type: XMOBILE Security Code: * TN: 1
Coverage Path 1: 164 COR: 3
Name: Blabla Coverage Path 2: COS: 1
Hunt-to Station:
STATION OPTIONS
Time of Day Lock Table:
XMOBILE Type: DECT Message Lamp Ext: 164
Display Module? y Message Waiting Type: ICON
Display Language: english Length of Display: 12x3
Mobility Trunk Group: 4 Calls Allowed: all
Configuration Set:
CELL PHONE NUMBER MAPPING
Dial Prefix:
Cell Phone Number: 164
Mapping Mode: both
-----------------------------------------------------------
Hope some of this will help.
We had to change mapping mode to BOTH
