Chapter 1 MAINTENANCE SERVICES
1-40
NWA-033627-001 Rev.4.0
95ch1001.fm
VoIP LOG COLLECTION
3: Own terminal/Blade type
• For station: STNX-XXXXXXXX (X-XXXXXXXX=STA. No. [1-8 digits])
• For VoIPDB: VoIPXXYYY (XX=Unit No. 01-50, YYY=VoIPDB Channel No. 001-128)
4: Connected party terminal/Blade type
• For station: STNX-XXXXXXXX (X-XXXXXXXX=STA. No. [1-8 digits])
• For VoIPDB: VoIPXXYYY (XX=Unit No. 01-50, YYY=VoIPDB Channel No. 001-128)
• For connected party: M_XXXXXXXX (XXXXXXXX=Logical Collection Position No.
[8 digits])
NOTE:
SIP is output as “connected party”.
5: IP address of connected party: XXX.XXX.XXX.XXX
6: Number of sent RTP packets: XXXXXXXX (8-digits fixed hexadecimal value)
7: Number of received RTP packets: XXXXXXXX (8-digits fixed hexadecimal value)
8: Number of received RTP packets lost: XXXXXXXX (8-digits fixed hexadecimal value)
• Conditions for call log collection of SIP trunk are as follows.
(a) Call log of SIP trunk is notified from SIP trunk to CPU blade when sending/receiving of RTP
packet are completed.
(b) For the number of RTP packets sent in call log, the number of transmissions of SIP trunk is
saved.
(c) For the number of RTP packets received in call log, the number of receptions of renewable
packets is saved.
• Conditions for call log collection of T.38 FAX are as follows.
(a) The number of packets sent, the number of packets received, and the number of receiving
packets lost in T.38 FAX communication can be displayed by using the existing call log
collection feature.
(b) Each number of packets in T.38 FAX communication is displayed in the order of the
description of (a) following the number of packets for voice communication.
APRIL/16/2010
