Vega Detailed Logging

Overview

We can enable Detailed logging in VEGA per module basis in order to speed up debugging.

VEGA has divided into multiple logical modules and each group has its own logging mechanism so depends on issue type we could enable detailed logging of that module which will help to track down the issue asap.

Enable default logs as mentioned in Vega Troubleshooting-Information page. This will help to get top level module information which is having an issue and then we can enable detail logging for that module.

Precaution  

Please make sure detailed loggings are not enabled during traffic (more than 0.5 CPS or so) where enabling detail logging can affect VEGA performance.

Detail loggings should ONLY be enabled in circumstances where we are facing issues like configuring VEGA, making 1 call and not working, CLID, PRI down/up issues etc.

Detail logging is purely for scenarios where we know enabling logs will not impact Vega performance such as just 1 call to reproduce the issue.

Please DO NOT enable details logging in a production environment where traffic keeps going constantly. 

Logging Modules

“debug help”  in Vega CLI will show you the list of all modules and their debugging level as defined in VEGA CLI Help section. 

Details of each module are defined in the following subsections.

SIP Module

This module is responsible for complete SIP call processing.

Whenever we see any issues like SIP calls getting rejected / calls are not going towards ISDN / media negotiation / T.38 fax etc we could enable detail logging of this module to troubleshoot further.

debug enable _sip ietf123456789   ( enabling complete SIP module logging, we could wisely choose logging level depends on our requirement and issue type). 

debug disable _sip ietf123456789  (disable complete logging)

ISDN Module

This module is responsible for all ISDN Call processing. 

Whenever we see some issues related to ISDN call processing like calls not routing to ISDN / calls not coming from ISDN / calls getting disconnect from ISDN etc, we could enable this module logging to troubleshoot further.

debug enable _isdn ietf123456789   ( enabling complete ISDN module logging, we could wisely choose logging level depends on our requirement and issue type). 

debug disable _isdn ietf123456789  (disable complete logging)

POTS Module

This module is responsible for all POTS related call control and supplementary services processing.

Whenever we see some issues related with POTS call processing like calls not routing to POTS/calls not coming from POTS/calls getting disconnect from POTS, supplementary services not working etc, we could enable this module logging to troubleshoot further.

debug enable _pots ietf123456789   ( enabling complete POTS module logging, we could wisely choose logging level depends on our requirement and issue type). 

debug disable _pots ietf123456789  (disable complete logging)

debug enable _default 4  (for pots supplementary services logging)

CAS Module 

This module is responsible for MFC-R2 protocol stack.

Whenever we see any issue in R2 protocol like link not coming up / CLID not coming or transmitting / abrupt call disconnect etc, we could enable this module logs to see low-level R2 protocol messages to understand end-2-end call flow.

debug enable _cas ietf123456789   ( enabling complete CAS module logging, we could wisely choose logging level depends on our requirement and issue type). 

debug disable _cas ietf123456789  (disable complete logging)

NOTE: Also refers to Vega R2 Debugging  

DSP Module

Whenever we see some issues related to DSP module then we could enable DSP module logging.

Issues could be like " Audio issue / DSP Error coming in console due to which calls are not connecting " etc.

debug enable _dsp ietf123456789   ( enabling complete DSP module logging, we could wisely choose logging level depends on our requirement and issue type). 

debug disable _dsp ietf123456789  (disable complete logging)

LANAPI Module

Whenever we see some issues related to LAN/Networking/DHCP/DNS etc, we could enable this module logging to troubleshoot further.

debug enable _lanapi ietf123456789   ( enabling complete LANAPI module logging, we could wisely choose logging level depends on our requirement and issue type). 

debug disable _lanapi ietf123456789  (disable complete logging)

ROUTER Module

This module is responsible for relaying the messages between different modules like passing a message from SIP to ISDN will go via this module.

Whenever we see some issues in dialplan or routing, we could enable this module logs to troubleshoot further.

debug enable _router ietf123456789   ( enabling complete ROUTER module logging, we could wisely choose logging level depends on our requirement and issue type). 

debug disable _router ietf123456789  (disable complete logging)

Ethernet Module

This is to look for Ethernet/NIC level issues.

debug enable _ethernet ietf123456789   ( enabling complete Ethernet module logging, we could wisely choose logging level depends on our requirement and issue type). 

debug disable _ethernet ietf123456789  (disable complete logging)

TN Module

This module is responsible for low-level ISDN protocol stack.

Whenever we like to see low-level ISDN protocol issues like incoming SETUP failed, call reference issue, no D-channel available, outgoing setup issue, ISUP message flow issues like no connect ack in response to connecting etc, we could enable this module logs to troubleshoot further.

debug enable _tn ietf123456789   ( enabling complete TN module logging, we could wisely choose logging level depends on our requirement and issue type). 

debug disable _tn ietf123456789  (disable complete logging)

Note: Generally we like to enable ISDN module logging as well in order to capture complete ISDN processing starting from protocol to call control.

MG/MC/MT Module 

These modules are responsible for Media/DSP and interface between DSP and SIP module.  So whenever we like to debug media related issues where we don't see anything wrong in SIP and in DSP then we could enable this logging as well depends on issue scenario. 

VEGA CLI Help 

admin  >debug help

 The following module specific diagnostics are defined

 _DSP

T1    :API   :Diagnostics from DSP API

  T2    :Select:DSP Codec and Channel Selection

  T3    :Decode:High level DSP message decode

  T4    :Queue :DSP command queue operation

  T5    :Detail:Detailed DSP message decode

  T6    :Download:DSP image download operation

  T7    :Config:DSP configuration

  T8    :DSPrx :Messages received from DSP

  T9    :DSPtx :Messages and Signals sent to DSP

_LANAPI

  T1    :NAT   :NAT diagnostics

  T2    :DNS   :DNS diagnostics

  T3    :Proxy :Internal LAN Proxy operation

  T4    :ATIErr:Error responses from ATI

  T5    :Routing:LAN routing

  T7    :PMsg  :Proxy Message Decode

  T8    :Profile:LAN Profiles

  T9    :LOWLEVEL:Diagnostics which may cause a system crash

_ISDN

  T2    :CB    :Control block management

  T6    :Q931Rx:Internal received Q.931 packet dump

  T7    :Q931Tx:Internal transmitted Q.931 packet dump

  T8    :RawRx :Raw received packet dump

  T9    :RawTx :Raw transmitted packet dump

_ROUTER

  T2    :cpg   :call presentation group

_POTS

  T1    :FXS   :FXS specifics

  T2    :call  :POTS Call

  T3    :IF    :POTS Interface

  T4    :port  :Physical port

  T5    :suppserv:Supplementary Services

  T6    :FXO   :FXO specifics

  T7    :mwi   :Visual Message Waiting

  T8    :media :POTS media control

_ETHERNET

  T2    :NIC   :Basic NIC calls

  T3    :ToLAN :NIC to LAN

  T4    :Looping:NIC packet looping

  T5    :PHY   :Basic PHY calls

  T6    :PHYREAD:PHY Read

  T7    :PHYWRITE:PHY Write

  T8    :MAC   :Basic MAC calls

  T9    :PHYSTATUS:PHY Status

_SIP

  T2    :timer :SIP session timer

  T3    :trani :Transaction layer info

  T4    :trant :Transaction layer trace

  T5    :sdp   :SDP encoding/decoding

  T6    :media :PROMPT media control and call control

  T7    :socket:SIP socket management

  T8    :proxy :proxy management (and DNSSRV)

  T9    :monlite:SIP monitor lite

_MT

  T2    :TPKT  :TPKT activity

  T3    :T38   :T38 activity

  T6    :ConnEv:Connection events

  T7    :ConnAn:Connection analysis

  T8    :PConn :Packet Connection activity

  T9    :TConn :TDM Connection activity

_TN

  T1    :TN_L1 :Telenetworks Layer 1

  T2    :TN_L2 :Telenetworks Layer 2

  T3    :TN_L3 :Telenetworks Layer 3

  T4    :TN_CC :Telenetworks Call Control

  T5    :TN_Host:Telenetworks Host

  T6    :TR_TMR:Telenetworks Timers

_MC

  T2    :Conf  :Conference API calls

  T3    :ConfIn:Conference Internal calls

  T4    :Sess  :Session API calls

  T5    :SessCB:Session call backs

_MG

  T1    :Tran  :Transfer API calls

  T2    :TranCB:Transfer call backs

  T3    :TranIn:Transfer internal calls

  T4    :Term  :Termination API calls

  T5    :TermIn:Termination internal calls

  T6    :TermCB:Termination call backs

  T7    :DSP   :DSP management

_CAS

  T1    :RBS_L1:CAS Layer 1

  T2    :RBS   :CAS RBS protocol

  T3    :TMR   :CAS timer

  T4    :R2    :CAS R2 protocol

  T5    :CAS-SM:CAS State Machine

  T6    :ABCD  :CAS ABCD signalling

  T7    :CAS-RG:CAS Register signalling

_CALL

  T2    :Bill  :Billing module

  T3    :Radius:Radius module

  T4    :QoStat:QoS statistics module

  T5    :RadiusHex:Radius module hex trace