SIPCallTrace on in CS1000E 7.0 2

[RyanEOD]

Good Morning!

Does anyone know what commands the "SIPCallTrace on" becomes when upgrading to 7.0? When trying to do it I now see I need an appName, of either tSLG or tSSG, and when trying to turn both of them on, I don't get any scrolling information when either trying to register a SIP phone or forcing traffic down my SIP trunks. Thanks for any assistance!

 

[KillianK]

might be of use

3.1.201 SIPCallTrace ch channelNum MsgRecv MsgRecv
This command turns on/off the SIP tracing.
channelNum is the channel number of the virtual trunk to trace. Values range from 0 - maximum channel number.
MsgRecv specifies if the messages sent to the specified channels should be traced. Values are ON or OFF.
MsgSend specifies if the messages sent from the specified channels should be traced. Values are ON or OFF.

oam> SIPCallTrace ch 033 on on
oam> 11/01/05 15:22:11 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:11 Recv chid:33 ip:192.168.19.50:5060 SIP INVITE

11/01/05 15:22:11 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:11 Send chid:33 ip:192.168.19.51:5060 SIP response 100

11/01/05 15:22:11 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:11 Send chid:33 ip:192.168.19.51:5060 SIP response 180

11/01/05 15:22:11 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:11 Recv chid:33 ip:192.168.19.50:5060 SIP method PRACK(7)

11/01/05 15:22:11 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:11 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:22:19 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:19 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:22:19 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:19 Recv chid:33 ip:192.168.19.50:5060 SIP method ACK(1)

11/01/05 15:22:19 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:19 Recv chid:33 ip:192.168.19.50:5060 SIP method other/unknown(6)

11/01/05 15:22:19 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:19 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:22:23 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:23 Send chid:33 ip:192.168.19.51:5060 SIP method BYE(2)

11/01/05 15:22:23 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:23 Recv chid:-1 ip:192.168.19.50:5060 SIP response 200

11/01/05 15:22:33 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:33 Recv chid:33 ip:192.168.19.50:5060 SIP INVITE

11/01/05 15:22:33 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:33 Send chid:33 ip:192.168.19.51:5060 SIP response 100

11/01/05 15:22:33 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:33 Send chid:33 ip:192.168.19.51:5060 SIP response 180

11/01/05 15:22:33 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:33 Recv chid:33 ip:192.168.19.50:5060 SIP method PRACK(7)

11/01/05 15:22:33 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:33 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:22:36 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:36 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:22:36 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:36 Recv chid:33 ip:192.168.19.50:5060 SIP method ACK(1)

11/01/05 15:22:36 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:36 Recv chid:33 ip:192.168.19.50:5060 SIP method other/unknown(6)

11/01/05 15:22:36 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:22:36 Send chid:33 ip:192.168.19.51:5060 SIP response 200
3.1.202 SIPCallTrace ch start_chNum end_chNum MsgRecv MsgSend
This command allows the tracing of a range of vtrk channels.
start_chNum is the channel number to trace. Values range from 0 - maximum channel number.
end_chNum is the cannel number to trace. Values range from 0 - maximum channel number, but needs to be greater than the start_chNum.
MsgRecv specifies if the messages sent to the specified channels should be traced. Values are ON or OFF.
MsgSend specifies if the messages sent from the specified channels should be traced. Values are ON or OFF.

oam> SIPCallTrace ch 033 38 on on
oam> 11/01/05 15:23:30 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:23:30 Send chid:33 ip:192.168.19.51:5060 SIP method BYE(2)

11/01/05 15:23:30 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:23:30 Recv chid:-1 ip:192.168.19.50:5060 SIP response 200

11/01/05 15:23:40 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:23:40 Recv chid:33 ip:192.168.19.50:5060 SIP INVITE

11/01/05 15:23:40 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:23:40 Send chid:33 ip:192.168.19.51:5060 SIP response 100

11/01/05 15:23:40 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:23:40 Send chid:33 ip:192.168.19.51:5060 SIP response 180

11/01/05 15:23:40 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:23:40 Recv chid:33 ip:192.168.19.50:5060 SIP method PRACK(7)

11/01/05 15:23:40 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:23:40 Send chid:33 ip:192.168.19.51:5060 SIP response 200


oam> 11/01/05 15:24:00 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:24:0 Recv chid:33 ip:192.168.19.50:5060 SIP method CANCEL(8)

11/01/05 15:24:00 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:24:0 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:24:00 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:24:0 Send chid:33 ip:192.168.19.51:5060 SIP response 487
3.1.203 SIPCallTrace num calling/called_number MsgRecv MsgSend
This command allows the tracing of SIP messags using the called and calling numbers. If the called or calling number of a vtrk session matches the number specified then the messages to and from the vtrk will be traced.
calling/called_number is the phone number to trzce on, number can be from 1 to 32 numeric digits and can be a partial calling/called number
MsgRecv specifies if the messages sent to the specified channels should be traced. Values are ON or OFF.
MsgSend specifies if the messages sent from the specified channels should be traced. Values are ON or OFF.

oam> SIPCallTrace 5500 on on
oam> 11/01/05 15:19:56 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:56 Recv chid:33 ip:192.168.19.50:5060 SIP INVITE

11/01/05 15:19:56 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:56 Send chid:33 ip:192.168.19.51:5060 SIP response 100

11/01/05 15:19:56 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:56 Send chid:33 ip:192.168.19.51:5060 SIP response 180

11/01/05 15:19:56 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:56 Recv chid:33 ip:192.168.19.50:5060 SIP method PRACK(7)

11/01/05 15:19:56 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:56 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:20:00 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:0 Recv chid:33 ip:192.168.19.50:5060 SIP method CANCEL(8)

11/01/05 15:20:00 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:0 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:20:00 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:0 Send chid:33 ip:192.168.19.51:5060 SIP response 487

11/01/05 15:20:16 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:16 Recv chid:33 ip:192.168.19.50:5060 SIP INVITE

11/01/05 15:20:16 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:16 Send chid:33 ip:192.168.19.51:5060 SIP response 100

11/01/05 15:20:17 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:17 Send chid:33 ip:192.168.19.51:5060 SIP response 180
11/01/05 15:20:17 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:17 Recv chid:33 ip:192.168.19.50:5060 SIP method PRACK(7)

11/01/05 15:20:17 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:17 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:20:21 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:21 Recv chid:33 ip:192.168.19.50:5060 SIP method CANCEL(8)

11/01/05 15:20:21 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:21 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:20:21 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:21 Send chid:33 ip:192.168.19.51:5060 SIP response 487

11/01/05 15:20:26 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:26 Recv chid:33 ip:192.168.19.50:5060 SIP INVITE

11/01/05 15:20:26 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:26 Send chid:33 ip:192.168.19.51:5060 SIP response 100

11/01/05 15:20:26 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:26 Send chid:33 ip:192.168.19.51:5060 SIP response 180

11/01/05 15:20:26 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:26 Recv chid:33 ip:192.168.19.50:5060 SIP method PRACK(7)

11/01/05 15:20:26 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:26 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:20:30 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:30 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:20:30 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:30 Recv chid:33 ip:192.168.19.50:5060 SIP method ACK(1)

11/01/05 15:20:30 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:30 Recv chid:33 ip:192.168.19.50:5060 SIP method other/unknown(6)

11/01/05 15:20:30 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:30 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:20:33 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:33 Recv chid:33 ip:192.168.19.50:5060 SIP method BYE(2)

11/01/05 15:20:33 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:20:33 Send chid:33 ip:192.168.19.51:5060 SIP response 200

3.1.204 SIPCallTrace num calling/called number NPI TON MsgRecv MsgSend
This command allows a user to trace SIP messages using the called and calling numbers. If the called or calling number of a vtrk session matches the number specified and the specified NPI and TON values match the call type, then the messages to and from the vtrk will be traced.
calling/called_num is the phone number to trace on. Number can be from 1 to 32 numeric digits and can be a partial calling/called number.
NPI specifies the numbering plan identifier for which calls using this numbering plan are to be traced. Values are:
0- ALL NPIs
1- Uknown
2- ISDN/telephone numbering plan (E.164)
3- Private numbering plan
4- E.163
5- Telex numbering plan
6- Data numbering plan
7- National standard numbering plan
TON specifies the type of number to use as a filter for tracing. Only calls using this TON setting will be traced.
0- All TONs
1- Unknown Number
2- International Number
3- National Number
4- Network Specific Number
5- Subscriber Number
6- L1 Regional Number
7- L0 Regional Number
MsgRecv specifies if the messages sent to the specified channels should be traced. Values are ON or OFF.
MsgSend specifies if the messages sent from the specified channels should be traced. Values are ON or OFF.

oam> SIPCallTrace num 5500 3 7 on on

The trace settings for Num: 5500, NPI: Private and TON: CDP were already available as follows:
Number : 5500
NPI : Undefined
TON : Undefined
MsgRecv: On
MsgSend: On
oam> 11/01/05 15:19:19 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:19 Recv chid:33 ip:192.168.19.50:5060 SIP INVITE

11/01/05 15:19:19 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:19 Send chid:33 ip:192.168.19.51:5060 SIP response 100

11/01/05 15:19:19 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:19 Send chid:33 ip:192.168.19.51:5060 SIP response 180

11/01/05 15:19:19 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:19 Recv chid:33 ip:192.168.19.50:5060 SIP method PRACK(7)

11/01/05 15:19:19 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:19 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:19:21 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:21 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:19:21 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:21 Recv chid:33 ip:192.168.19.50:5060 SIP method ACK(1)

11/01/05 15:19:21 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:21 Recv chid:33 ip:192.168.19.50:5060 SIP method other/unknown(6)

11/01/05 15:19:21 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:21 Send chid:33 ip:192.168.19.51:5060 SIP response 200

11/01/05 15:19:23 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:23 Recv chid:33 ip:192.168.19.50:5060 SIP method BYE(2)

11/01/05 15:19:23 LOG0006 SIPNPM: SIPCallTrace: 11/1/5 15:19:23 Send chid:33 ip:192.168.19.51:5060 SIP response 200

 

[KillianK]

maybe you might need to change the level of information output

3.1.214 syslogLevelSet task, level
This command controls the printing of detailed information from a task. To change information for multVGMCe tasks, the command is entered multVGMCe times.
The parameter task specifies the module for this entry of the command. The name of the task as printed by the logShow (VGMC), syslogShow or i (VGMC / SS) command is used.
The following list explains what some of the tasks functions are.
tSnmpd SNMP daemon task
tSntpsTask SNTP Server task
tXA
tA07 SSD driver interface
tRDP
tMAM Maintenance Admin Module
tMVX_XSPY Telogy SPY (debugger)
tMVX_DIM Telogy Dsp Interface Module
tOMM Operational Measurement Module
tVTM Virtual Terminal Manager
tVTI Virtual Terminal Interface
tSET Digital Set Emulator
tCSV Connect Server
tTPS Terminal Proxy Server
tTCK TPS Socket Task
tUMS UMS Server
tUMC UMS Client
tVGW Voice Gateway
tRTP Real Time Protocol
tRTCP Real Time Control Protocol
tTelnetOutTask Telnet output task
tTelnetInTask Telnet input task
tyLstnr
tShell VxWorks Shell task
The parameter level sets what kind of information is printed per the list below. Setting a task to a level allows messages of that level and lower to print. By default, most tasks are set to Info. When troubleshooting a problem, it is often useful to set the level to Debug to get more detailed information from a task.
NOTE: the volume of messaging printed by most tasks when set to Debug level dictates this command be used under light traffic loads. Be careful when enabling on a busy card!
0 - Emergency, system is unusable
1 - Alert, action must be taken immediately
2 - Critical, critical conditions
3 - Error, error conditions
4 - Warning, warning conditions
5 - Notice, normal but significant condition
6 - Info, informational
7 - Debug, debug level messages
Here’s an example of the command:

-> syslogLevelSet tMAM, 7
value = 6 = 0x6
3.1.215 syslogShow
On the SS, logShow does not provide much information, so this command must be used as shown below to get the tasks’ log output level. On the VGMC, this is similar to the logShow but it prints just the task and level info and only works from the VxWorks shell. Used in conjunction with syslogLevelSet (see section syslogLevelSet ).
The output on the SS (note this is not only the LTPS tasks but includes the VTRK and Gatekeeper tasks)

-> syslogShow
Task Level
-------------------- -------
tSysWork none
tExcTask none
tLogTask none
tAioWait none
tAioIoTask1 none
tAioIoTask0 none
tNetTask none
tPortmapd none
tFtpdTask none
tTftpdTask none
tWdbTask none
tRptd none
tLogin none
tLogin none
tRLogind none
tTelnetd none
tSnmpd none
tPxTimer none
tbootpd none
tSNTPC Info
tRDP Info
tMAM Info
tOMM Info
tELC Info
tVTM Info
tVTI Info
tSET Info
tCSV Info
tTPSAR Info
tTPS Info
tTPSARReceive none
tfwBk Info
tUMS Info
tUMC Info
tVTK Info
tNPM Info
tXMSG Info
tHTTPd none
tHTTPd none
tHTTPd none
tHTTPd none
shell none
tPBX Info
tTelnets38 none
tLogin none
tTelnetc38 none
shell none
tShell Info
value = 5 = 0x5
And the output on the SMC:

-> syslogShow
Task Level
-------------------- -------
tExcTask none
tLogTask none
tAioWait none
tAioIoTask1 none
tAioIoTask0 none
tPcmciad none
tDcacheUpd none
tNetTask none
tTelnetd none
tPortmapd none
tFtpdTask none
tTftpdTask none
tSnmpd none
tSyslogd none
tMonTask none
tPxTimer none
tbootpd none
tSNTPC none
baseMMintTask none
tXA Info
tA07 Info
tRDP Info
tMAM Info
tMVX_XSPY none
tMVX_DIM Info
tOMM Info
tPBX Info
tELC Info
tVGW Info
tRTP Info
tRTCP Info
tXMSG Info
midnightTask none
tShell none
tTelnetOutTask none
tTelnetInTask none
tyLstnr none
value = 5 = 0x5

 

[RyanEOD]

Coming back to this and messing around with it and still not getting SIP traffic. I know it has to be something small, but I can't figure it out for the life of me.