Calls Between Oxe User And Icm Users Failed If Ofs Server Is Managed On The Opentouch Server; Icm User Aren't Reachable From Attendant On Oxe; Opentouch Pstn Outgoing Calls To Gsm Leads To Sip Error 502; Call To Mobiles Are Cut - Alcatel-Lucent OpenTouch Troubleshooting Manual

Hide thumbs Also See for OpenTouch:
Table of Contents

Advertisement

Alcatel-Lucent OpenTouch R1.x Troubleshooting guide
Diagnosis : This is due to the method used by actis to calculate the value of the paramao3 (Total nb of
trunks). In fact actis use the number of simultaneous calls authorized (in fact the value of the lock 188: SIP
Network Link) to calculate the number of trunks. In some case, if the number of simultaneous calls is small,
actis calculate trunks for mini-SIP trunk groups instead a normal SIP trunk group.
Check in the hardware.mao and offerName.hw files that paramao3 is >= to 150, if not you can modify it
directly in these 2 files (open them with notepad or wordpad)
PRODUCT OXE
OPS
E1710 ABARAR0270EA
OPS_MAO 16.3
OPS_OXE_Release 10.0
MAO_OPS 001
MAO_OXE_Release 10.0
VERS_4400 j1.410.34
PARA_MAO 1
57787
PARA_MAO 2
862
PARA_MAO 3
80 --> 150
PARA_MAO 4
1632
21.5.4 Calls between OXE user and ICM users failed if OFS server is managed on the
OpenTouch server
External sip gateway to ice must be managed with FQDN for remote domain
parameter and port 5260
External sip gateway to OFS must be managed with IP address and port 5260

21.5.5 ICM user aren't reachable from attendant on OXE

If there is no attendant individual call prefix for attendant when she calls an ICM user invite is going
from OXE to ICE
with sip trunk name of oxe in from field.
Extensible services reject the call due to unknown number
Manage attendant individual call prefix

21.5.6 OpenTouch PSTN outgoing calls to GSM leads to SIP error 502

oxe sends a Disconnect after 3 sec following the progress
Increase timer T310 to 350 in mgr/external service/trunk QOS/trunk QOS 31

21.5.7 Call to mobiles are cut

Symptom : Call to mobiles are cut
Solution : system/ Other System Param./Go down hierarchy/External Signalling Parameters/Consult/Modify
Set "Deactivate Path Replacement" : True

21.5.8 OpenTouch blind transfer 8082-IPTouch MyIC Phone call flow fail

Symptom : OpenTouch blind transfer 8082-IPTouch-8082 call flow fail
Scenario : Starting a call from OT user (8082) to an IPTouch (standar user). Take the call on the IPTouch,
and then dial directly extension number for a second OT user (8082), then blind transfer (press the dynamic
key for "transfer). No audio in that conversation. PS: transfer after party answer is OK.
Solution: Create a DPNSS prefix:
Consult/Modify: Prefix Plan
Number : #98
Prefix Meaning + Local Features
Local Features + Pabx address in DPNSS
Ed.15 / June 2013
VERS_OPS_4400 2.0.2
165/182
TG0064

Advertisement

Table of Contents
loading

Table of Contents