(1.
)   Current backup configuration:
       ==================================
       Navigate WebUI, Tasks -> System -> Backup/Restore Config -> Backup
       Configuration. Refer:
       https://support.sonus.net/display/UXDOC90/Backing+Up+Data
       (2.) Syslog:
       ==============
       To collect syslog, you can use EITHER a 'Remote Log Server with LX' OR 'local
       logs'.
       If you use Remote Log Server, navigate to "Settings" -> "Logging Configuration"
       -> "Remote Log Servers" and set global logging level to "Informational".
       Refer:
       https://support.sonus.net/display/UXDOC110/Managing+Remote+Log+Servers
       https://support.sonus.net/display/ALLDOC/Log+Exchange+-+LX
       https://support.sonus.net/display/LXDOC/Configuring+LX+as+a+Syslog+Server
       +on+Sonus+Products
       If the SBC is capable of local logging, refer:
       https://support.sonus.net/display/UXDOC110/Managing+Local+Logs
       Next, navigate to "Settings" -> "Logging Configuration" -> "Subsystem" and raise
       logging level of the following subsystems
       to:
       - SIP Stack Service [DEBUG],
       - Call Routing Service [DEBUG],
       - Common Call Control [DEBUG] ,
       - Media Stream Control [DEBUG],
       - ISDN Protocol [DEBUG], (If call flow involve PSTN)
       - CAS and Telephony Interface Process [DEBUG], (If FXO/FXS on SBC is used)
       Refer:
       https://support.sonus.net/display/UXDOC110/Creating+and+Modifying+Subsyste
       m+Logging
       Lastly, try to duplicate the problem.
       WARNING: Don't forget to turn this off afterward to avoid overloading the box.
       (3.) Alarm History:
       ==============================
       Please export Alarm/Event history: Diagnostics > Logs > Alarm/Event History >
       Export as CSV > Attach to the case.
1) Attach the configuration file, Tasks -> System -> Backup/Restore Config -> Backup
Configuration.
(https://support.sonus.net/display/UXDOC90/Backing+Up+Data)
2) Call Trace:
**Navigate to "Settings" -> "Logging Configuration" -> "Local Log Configuration" &
"Remote Log Servers" and set the Global Log level to "INFORMATIONAL".
**Then navigate to "Settings" -> "Logging Configuration" -> "Subsystems" and raise the
logging level of the following subsystems
to "Debug":
- SIP Stack Service,
- Call Routing Service,
- Common Call Control,
- Media Stream Control,
- ISDN Protocol, (If call flow involves PSTN)
- Telephony Interface Process (If FXO/FXS on SBC is used, or E1/T1 port-related logging)
- CAS Protocol (If FXO/FXS or ISDN CAS is used)
Remote Log Server:
SBC 1000: The 1k doesn't contain the HDD and all log must be collected to Remote Log
Server
( https://support.sonus.net/display/UXDOC90/Managing+Remote+Log+Servers ).
LX debug log Parser and Syslog Server should be used and setup as a Log Server:
https://support.sonus.net/display/LXDOC/
Configuring+LX+as+a+Syslog+Server+on+Ribbon+Products
Please refer to
'https://support.sonus.net/display/UXDOC90/Creating+and+Modifying+Subsystem+Logging'
for help.
You can use LX as Remote Log server:
(You can install LX to you PC)
See:
3) As there is an audio issue (per your description), we need a packet capture to check on the
media packets.
When doing the packet capture, please enable the Media for RTP. This will automatically
capture all interfaces going through the SBC.
https://support.sonus.net/display/UXDOC90/Working+with+Packet+Capture
https://support.sonus.net/display/UXDOC90/Packet+Capture+-+Best+Practice
Important Note: Once you have done collecting the logs and the test call, please revert the
settings to avoid overloading the SBC.
Another IMPORTANT NOTE: {Both the SBC Logs and PCAP have to be taken
simultaneously}
4) Alarm History:
==============================
Please export Alarm/Event history: Diagnostics > Logs > Alarm/Event History > Export as
CSV > Attach to the case.
- Tại CNC sẽ có 01 PC kết nối được vào giao diện quản trị của thiết bị SBC: thựcc hiện truy
cập PC này để vào giao diện quản trị SBC
- Tuy nhiên PC này sẽ không cài được phần mềm và nhận log được từ SBC nên cần nhờ CNC
cho remote vào 01 PC khác của họ nằm ngoài FW để nhận log
- Truy cập remote vào PC đó để cài phần mềm LX 2.1 và nhận log từ thiết bị SBC cần lấy log
Các bước cài và setup LX
- Config LX làm Syslog server:
https://doc.rbbn.com/display/LXDOC/Configuring+LX+as+a+Syslog+Server+on+Ribbon+P
roducts
Cấu hình SBC đẩy log tới PC cài LX
- Cấu hình địa chỉ IP của PC nhận Log làm remote server
https://doc.rbbn.com/display/UXDOC61/Managing+Remote+Log+Servers