Below is a list of opened anomaly reports to be fixed in a further patch
Key Summary
CROXE-18375 Alpha nu11: most of time no access LDAPS - backtrace UPBM
CROXE-16392
When Attendant does broker call in RAINBOW ringing, not possible to answer the call from Rainbow user.
CROXE-16520 M5-NRT MD1: Noise is observed in double forward scenario OT set involved
CROXE-16550 M5-NRT MD1:Noise occurred in RBT of external user when network transferred to seplos
CROXE-17061
M5-EEGW: About 50 sets resetted while launching IPNOSIS traffic testing for (15k registration + 7k calling) in 4096 key size
CROXE-17492 AlphaM5 nu12 : no more incidents for several days -mailsys defunct
CROXES-25538 OT17/OTC_PC/RQOT-473: Manager/Assistant: for one of my users Screening rule doesn't work
CROXE-17589
M5 MD2-NRT-When R+OXE calls NOF & call forwarded to external,after answer in display of rainbow **** came instead of no(External no/Name)
CROXE-17727 M5-NRT: Coupler(GD3) Backtrace is observed in Thales node during RUNTEL CROXE-17749 FSNE : lanpbxbuild PROXY ADRESS always visible even there is no information
CROXE-17870
Alpha - After switchover, OXE NU12 Crystal 3 reset immediately after (many alpha devices reset) then works fine.
Key Summary
CROXE-18025 M5NRT MD1 : One way voice path observed in NEAN call recording with TDM set CROXE-18403 M5 MD2-NRT-After bascul in conference there is no voice in SIP ISDNTLS
CROXE-18445 OXE/M5 :Wrong language displayed for french in IPDSP
CROXES-25257 OXE:\\M5: Display is not correct when "forbid all actions softkey in conversation " is set to yes CROXES-25267 OXE/M5 : Incident 6052 not displayed while using "incout -3" tool
CROXE-18609 M5 NRT : No voice when network set makes supervised transfer the call to rainbow CROXE-18622 NRT-M5 MD2-No RBT in network sip isdn tls call.
CROXE-18769
After blind transfers : some cases of no RBT/no audio with SEPLOS/noise in attendant and pilot to external
CROXE-18826 defense to replace passwd corrupted file is no more working
CROXE-18882 [Related] : DTMF are sent twice: by device in RTP and by OXE in ABCF
CROXE-18916
OXE M5: dumpPhonecos tool needs to be updated with all the fields of noe_phone_cos structure
CROXE-18939
M5-NRT: Unwanted missed Call log stored in tandem sets when second incoming is attended in secondary tandem
Key Summary
CROXE-18845 OXE M5 in spatial redundancy: No voice when call made to rainbow user with WRG as 1.75.6 CROXE-15439 M5: Desk sharing Network logon is not working in NOE 3G
CROXE-16040 M5- Initialization of INTIP3B with softMSM is not ok
CROXE-14989 Reset cause not mentioned in incinfo tool for the incident number 426
CROXE-18357
M5-NRT : Once FSNE Certificate Expires,the Terminals configured with same tftp are not coming in service with valid certificate even after factory reset.
CROXE-16213 M5- OXE- Premium S set (8078S) changes from NOE to SIP randomly
CROXE-18847 Alpha - 8078s - Suddently the USB speaker phone is no more recognized by the PC CROXE-18901 Alpha - 8078s - after desactivate /reactivate USB speaker phone, the device reset
CROXE-18908 Alpha - 8078s - Why bluetooth icon blinks when USB speaker phone is activate by pc audio CROXE-17774 Alpha - Unexpected reset of some noe3gee after node bascul
CROXE-18634 M5-NRT : Set Movement for IPv6 users is failed and set persists registration page itself CROXE-18796 M5:Support of IPv6 on 8088: New binary upgrade of 8088 user in IPv6 mode is failed CROXE-18824 Alpha - 8088 - Device is locked on boot step with admin screen
CROXE-18828 Alpha - 8088 - When USB key is plug to collect log, android media process crash CROXE-16687 OXE-M5-NRT: CTL verification is not happening in IPDSP
CROXE-17059 M5 Direct RTP T7: No MOH is present in SIP ABCF call between OXE and OXO CROXE-18260 M5 NRT ; Unable to modify ds-start-tls field as True in 8770 v4.2.12
CROXE-18576 OXE M5 : Unable to access 8770 server after upgraded to v4.2.13.1.a CROXE-18670 Alpha - 8168s - Device reset regularly
CROXE-15927 OXE M5: MIPT sets are not connected in CISCO wifi router
CROXE-18894
M5:Support of IPv6 on 8088: Reset of 8088 set in PCS rescue mode leads 8088 user into Out Of Service
CROXE-18895 M5:Support of IPv6 on 8088: PCS rescue of IPv6 8088 user is not working
18 TECHNICAL SUPPORT
Technical support will be provided to certified ACSE or ACFE engineers. The engineer must provide the valid SMS/SES or SPS contract id (Support processes available on the Business Portal under the heading Customer Support > Technical Support > Support processes).
Before contacting Alcatel's Business Partner Support Center (ABPSC), make sure that you have consulted:
The Troubleshooting Guides (Diagnostics support guides) where they exist and perform the actions suggested for your system problem (available on the Business Portal under the heading Customer Support > Technical Support > Technical Documentation Library.
The Technical Knowledge Center tool to perform a search, get a result, print the article or send it by email. This is the Alcatel-Lucent Enterprise Customer Care knowledge tool for Alcatel-Lucent Communications and Network solutions (available on the Business Portal under the heading Customer Support > Technical Support > Technical Knowledge Center ): Technical Knowledge Center
19 INTEROPERABILITY with Third-Party applications
In case of interoperability with Third-Party applications, it is highly recommended to verify the interoperability either by contacting the Third-Party supplier or by checking the existence of a valid “InterWorking Report” on the Business Portal.
Technical support will be provided only in case of a valid InterWorking Report and in the scope of the features which have been certified. That scope is defined by the InterWorking report via the tests cases which have been performed, the conditions and the perimeter of the testing as well as the observed limitations. All this being documented in the IWR. The certification does not verify the functional achievement of the AAPP member’s application as well as it does not cover load capacity checks, race conditions and generally speaking any real customer's site conditions.
Any possible issue will require first to be addressed and analyzed by the AAPP member before being escalated to ALE.
For any request outside the scope of this IWR, ALE offers the “On Demand Diagnostic” service where assistance will be provided against payment.
20 RESTRICTIONS
Restrictions to take into account in MD2:
- VNA: DTMF are sent twice: by device in RTP and by OXE in ABCF. Meaning application not functioning for manipulations that need DTMF sending. Fix expected in MD3. Internal report: CROXE-18882 - 8088 set in ipv6 mode: not functioning with PCS. Unknown date of fix
- 8088 set in ipv4 mode: not functioning with PCS. Fix (firmware) to be provided in MD3 - IP tickets on xBS:
o Loss of tickets
o No view of handover situation (future development in xBS R200 where 1 ticket will be generated per handover)
- Cloud Connect: a specific context in the Cloud servers will make the incident manager (mailsys) not functioning anymore. Meaning no more incidents will be recorded & emitted. A restart of “mailsys” will make it work again. Fix expected asap. Internal report: CROXE-17492
- SUOTA: put to OFF by default & translations. In RBS & XBS context SUOTA has caused major issues like boards reset, set slowed down or display “no system answer”…
INFO SUOTA: a hot fix can be asked to technical support if SUOTA feature is needed in RBS/IBS context
21 README/ LIST OF FIXES
The list of fixes can be found in the delivery of the static & dynamic patches:
<dhs3mgr>\<PATCH NAME>readme (text file)
It also shows the name & versions of the components being modified from the previous patch.
The anomaly reports that are fixed have the tags “RA CROXES” or “RA CROXE” followed by the internal ALE reference & a short description of the reporter.
New components have the tag “New”
Submitting a Service Request
Please connect to our eService Request application.
Before submitting a Service Request, please be sure:
The application has been certified via the AAPP if a third party application is involved.
You have read the release notes that list new features, system requirements, restrictions, and more, and are available in the Technical Documentation Library.
You have read through the related troubleshooting guides and technical bulletins available in the Technical Documentation Library.
You have read through the self-service information on commonly asked support questions and known issues and workarounds available in the Technical Knowledge Center.