Technical Helpweb

- more articles

How to read SwitchKit messages.log with channel ownership logging enabled

Introduction:  

Debugging certain application issues with either Dialogic® MSP SwitchKit® Development Environment or Dialogic® CSP SwitchKit® Development Environment may require information about when an application gains or loses ownership of a channel.  

This logging is disabled by default as it requires more space on the host's hard drive and increases the amount of resources SwitchKit needs to run.

See also: How to enable channel ownership logging 

This article provides an examples of logs that are created by this option and explains some of the various types of messages that turning on channel ownership logging will enable.

Details:   

When this log is enabled, application ownership changes of each channel assigned to the LLC will be logged to to the messages log. 

This is a list of common scenarios where a gain or loss of ownership occurs and a sample message from the messags.log showing the scenario occurring:

Gain of ownership
 

 - RFS via the watchChannelGroup method

//inbound RFS message caused by an inbound call to the switch
Dec 13 2010 11:07:24 X2000 ->H201  : 00 2d 00 16 00 00 01 0d 03 00 00  03 00 05 01 02 12 24 01 07 06 01 00 07 02 20 01 09 01 00 1d 03 80 90 a2  04 04 01 d0 58 39 03 05 7c 03 80 90 a2 0a 04 01 d3 53 03
//message printed immediately after the RFS above  showing the application(201) get ownership after AssignNotifyMsg is sent for the smallest channel group (SS7In) that the channel (span 0x00 channel 0x03) is assigned to.
Dec 13 2010 11:07:24 ChanMgmntInfo(Channel::selectNewOwnerFromWatchers): AssignNotifyMsg being sent for smallest group SS7In to app(201) as owner of (sp:(0x00) ch:(0x03) in state:(Idle))
Dec 13 2010 11:07:24 ChanMgmntInfo(CH_Idle::handleIncomingMsg): Assigning app(201) as owner of (sp:(0x00) ch:(0x03) in state:(Idle)

 - requestOutseizedChannel

//outseize message generated by application
Dec 13 2010 12:00:25 H REQ ->X2000 : 00 2c 00 00 00 00 01 0d 03 00 00 00 02 01 0a 00 02 12 14 01 02 0a 07 03 11 05 88 26 03 10 04 07 03 10 05 88 26 53 10 
Dec 13 2010 12:00:27 H LLC =>H REQ : 00 2c 00 00 00 00 10 (orig msg was 00 2c 00 00 00 00 01 0d 03 00 00 00 02 01 0a 00 02 12 14 01 02 0a 07 03 11 05 88 26 03 10 04 07 03 10 05 88 26 53 10 )
//Assigning application id 200 channel 0x00 span 0x00
Dec 13 2010 12:00:27 ChanMgmntInfo(CH_Outseizing::outseizeSuccessful): Assigning app(200) as owner of (sp:(0x00) ch:(0x00) in state:(Outseizing))

Loss of ownership

 - sk_returnChannel

//this release message is is what triggers the application (201 )to send sk_returnChannels() to free up the channel's ownership
Dec 13 2010 12:21:56 H LLC ->X2000 : 00 69 00 1a 00 
Dec 13 2010 12:21:56 X2000 ->H201  : 00 69 00 1a 00 00 01 0d 03 00 00 07 01 02 12 02 10 00
//This is the application calling sk_returnChannels and the llc then freeign up the channel for a future call.
Dec 13 2010 12:21:56 ChanMgmntInfo(ChannelController::handleReturnChannelMsg): Calling returnChannel on (sp:(0x00) ch:(0x07) in state:(Reserved)) for app(201)
Dec 13 2010 12:21:56 ChanMgmntInfo(ChannelManager::returnChannel): Called unreserved (sp:(0x00) ch:(0x07) in state:(Reserved)) for app(201)
Dec 13 2010 12:21:56 ChanMgmntInfo(CH_Reserved::unreserve): Clearing ownership for app(201) on (sp:(0x00) ch:(0x07) in state:(Reserved))

 
 - DS0 of purge or out of service

//purge message that cleared ownership
Dec 13 2010 12:10:23 X2000 ->H1,10 : 00 42 00 62 00 00 01 0d 03 00 00 05 00 12 
Dec 13 2010 12:10:23 H LLC ->X2000 : 00 42 00 63 00
//message in logs indicating that owernship has been lost
Dec 13 2010 12:10:23 ChanMgmntInfo(CH_OutOfService::handleIncomingMsg): Clearing ownership for app(201) on (sp:(0x00) ch:(0x05) in state:(Out of Service))

 - Termination of application

//before this point in the trace the below channel was assigned to an  application that died
Dec 13 2010 11:09:23 H LLC ->X2000 : 00 69 00 17 00
//since the application has died, when thechannel release message comes in for it LLC does not know where to route it to so the channel is in an orphaned state
Dec 13 2010 11:09:23 ChanMgmntError(CH_Orphaned::handleIncomingMsg): Exception NoAppsWatching((sp:(0x00) ch:(0x04) in state:(Orphaned)))
Dec 13 2010 11:09:23 X2000 ->H     : 00 69 00 17 00 00 01 0d 03 00 00 04 01 02 12 06 0c 01 12 02 81 90

 
- Auto return channels clearing ownership

This scenario is triggered when a release or DS0 status messages comes in on a channel opn an llc that has SK_AUTO_RETURN_CHANNELs set to 1 to automatically clear ownership

Dec 13 2010 11:07:57 ChanMgmntInfo(CH_InUse::handleIncomingMsg): AutoReturn clearing app(201) as owner of (sp:(0x00) ch:(0x03) in state:(In Use))
//channel released with data message showing the call releasing
Dec 13 2010 11:07:57 X2000 ->H201  : 00 69 00 16 00 00 01 0d 03 00 00 03 01 02 12 02 10 00

Product List:

Dialogic® CSP SwitchKit® Development Environment

Dialogic® MSP SwitchKit® Development Environment