Debugging Call Ctrl and SIP Messages

Expand / Collapse
 

Debugging Call Ctrl and SIP Messages


Overview

Debugging is turned on by default after Call Ctrl installation and will collect all SIP and Application messages as a result. Debugging should be the first thing to turn on and check when experiencing problems which are not evident after double checking general settings.

Background

There are many issues that can arrise when experiencing issues with Call Ctrl and the phone system.

Resolution

To turn on/off Debugging:

  1. Launch the Settings window by either selected Edit/Settings from the main menu or right-clicking the Call Ctrl tray icon and selecting Settings.
  2. Ensure the first tab, SIP Settings is selected. Check or Uncheck the Debugging Enabled checkbox.
  3. Call Ctrl requires a restart to either disable or enable debugging.

NOTE:It is recommended that after your initial configuration of Call Ctrl that Debugging be disabled. Debugging should only be enabled on initial configuration or when troubleshooting a phone device or Call Ctrl installation.

To view debugging results:

For each Windows user profile for which Call Ctrl is configured there is a seperate CallCtrlDebug file and is located in the following directory with the file name CallCtrlDebug.txt:

  • Vista or Windows 7
    C:\Users\ <<USERNAME>> \ AppData\Local\CTRL_IT_Inc\
    Variables can be used: %USERPROFILE%\AppData\Local\CTRL_IT_Inc\

  • XP
    C:\Documents and Settings\ <<USERNAME>> \Local Settings\Application Data\CTRL_IT_Inc
    Variables can be used: %USERPROFILE\Local Settings\Application Data\CTRL_IT_Inc

NOTE:The default debug text file is called CallCtrlDebug.txt. CallCtrlDebug may have a differant name which corresponds to the value located in CallCtrl.config setting CallCtrlDebugFile.

Debug file contents:

The following is the header containing the settings used for each application startup when debugging and the SIP client is initialized.

--------------------------------------------    
Logging Enabled: 1/1/2009 12:00:00 PM    
--------------------------------------------      
--SETTINGS----------------------------------     
SPA-9000 Address: 10.1.1.91    
SPA-9000 Port: 6060      
SPA-Series Phone Address: 10.1.1.95    
SPA-Series Phone Name: Steve        
CallCtrl Port: 5060-5061

The following is an example of a Call Ctrl generated error message. Performing a search for the value can provide valuable insight to all Call Ctrl errors that may not be displayed to the users.

--CALL CTRL ERROR--------------------------- 

Troubleshooting with Debug File

Summary of Call Ctrl initialization to SPA-9000:

The following SIP traces excerpt provides a good example of a working configuration. There are a few mandatory steps which must take place in order for Call Ctrl to establish communitation with the device to which it is configured to manage

  1. Call Ctrl REGISTER to SPA-9000 and recieves a 200 in response.
  2. Call Ctrl SUBSCRIBE to SPA-9000 and recieves a 200 OK in response.
  3. Call Ctrl NOTIFY (Send) to SPA-9000 and recieves a 200 OK in response.
  4. SPA-9000 NOTIFY (Recieve) to Call Ctrl and sends 200 OK in response.

Detail of Call Ctrl initialization to SPA-9000:

  1.  
    SUBSCRIBE to SPA-9000   
    SUBSCRIBE sip:Steve@10.1.1.91:6060 SIP/2.0   
    Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK-72327232   
    Max-Forwards: 70   
    From: <sip:vista@10.1.1.91>;tag=1471727439   
    To: <sip:Steve@10.1.1.91>   
    Call-ID: 168819943-1833765715-2074676046   
    CSeq: 2 SUBSCRIBE   
    Contact: <sip:vista@10.1.1.101:5060>  
     Content-Length: 0   Expires: 3600  
     Event: x-spa-cti  
    User-Agent: Call Ctrl 1.0 Steve       
    
    Response OK from SPA-9000  
    SIP/2.0 200 OK   
    To: <sip:Steve@10.1.1.91>;tag=dbaa86f56de58d   
    From: <sip:vista@10.1.1.91>;tag=1471727439  
    Call-ID: 168819943-1833765715-2074676046   
    CSeq: 2 SUBSCRIBE   
    Via: SIP/2.0/UDP 10.1.1.101:5060;branch=z9hG4bK-72327232   
    Server: Linksys/SPA9000-6.1.5  
    Expires: 3600   
    Allow-Events: talk, hold, conference, x-spa-cti   Content-Length: 0      
    
  2.  
    NOTIFY to SPA-9000 (Send)   
    NOTIFY sip:sw-vista@10.1.1.101:5060 SIP/2.0   
    Via: SIP/2.0/UDP 10.1.1.91:5080;branch=z9hG4bK-3c8cf2b5;rport   
    From: <sip:Steve@10.1.1.91>;tag=3ddc74fd77168c5a  
     To: <sip:sw-vista@10.1.1.91>;tag=44371761   
    Call-ID: 728313783-2100927785-1430562479   
    CSeq: 38056 NOTIFY  
    Max-Forwards: 70   
    Event: x-spa-cti   
    User-Agent: Linksys/SPA9000-6.1.5   
    Subscription-State: terminated   
    Allow-Events: talk, hold, conference, x-spa-cti  
    Content-Length: 0       
    
    Response OK from SPA-9000   
    SIP/2.0 200 OK   
    Via: SIP/2.0/UDP 10.1.1.91:5080;branch=z9hG4bK-3c8cf2b5;rport   
    From: <sip:Steve@10.1.1.91>;tag=3ddc74fd77168c5a   
    To: <sip:sw-vista@10.1.1.91>;tag=44371761   
    Call-ID: 728313783-2100927785-1430562479   
    CSeq: 38056 NOTIFY   
    Content-Length: 0  
    Event: x-spa-cti   
    User-Agent: Call Ctrl 1.0 Steve       
    
  3.  
    NOTIFY from SPA-9000 (Recieve)   
    NOTIFY sip:sw-vista@10.1.1.101:5060 SIP/2.0   
    Via: SIP/2.0/UDP 10.1.1.91:5080;branch=z9hG4bK-268e1b13;rport   
    From: <sip:Steve@10.1.1.91>;tag=dbaa86f56de58d  
    To: <sip:sw-vista@10.1.1.91>;tag=1471727439   
    Call-ID: 168819943-1833765715-2074676046  
    CSeq: 3635 NOTIFY   
    Max-Forwards: 70  
     Event: x-spa-cti   
    User-Agent: Linksys/SPA9000-6.1.5   
    Subscription-State: active;expires=3600   
    Allow-Events: talk, hold, conference, x-spa-cti   
    Content-Length: 1365   
    Content-Type: application/x-spa-status     
    <spa-status state="full">
    <phone mac="00000000" name="Steve" sw="6.1.3(a)" hw="1.0.3(6776)" nl="6" nc="12" model="SPA-962" serial="11111111"/>   
    <ext id="1" uri="200@10.1.1.91:6060" reg="F" dnd="F" suid="200" cfwd=""/>   
    <ext id="3" uri="400@10.1.1.91:6060" reg="F" dnd="F" suid="400" cfwd=""/>   
    <ext id="4" uri="200@10.1.1.91:6060" reg="F" dnd="F" suid="100" cfwd=""/>   
    <ext id="5" uri="200@10.1.1.91:6060" reg="F" dnd="F" suid="101" cfwd=""/>   
    <ext id="6" uri="200@10.1.1.91:6060" reg="F" dnd="F" suid="102" cfwd=""/>  
     <call id="1" ref="190" state="idle" ext="1" share="T"/>   
    <call id="2" ref="2" state="idle" ext="1" share="F"/>   
    <call id="3" ref="57" state="idle" ext="3" share="T"/>   
    <call id="4" ref="6" state="idle" ext="4" share="T"/>   
    <call id="5" ref="2" state="idle" ext="5" share="T"/>   
    <call id="6" ref="5" state="idle" ext="6" share="T"/>   
    <call id="7" ref="15" state="idle" ext="1" share="T"/>   
    <call id="8" ref="0" state="idle" ext="1" share="F"/>   
    <call id="9" ref="1" state="idle" ext="3" share="T"/>   
    <call id="10" ref="1" state="idle" ext="4" share="T"/>   
    <call id="11" ref="1" state="idle" ext="5" share="T"/>   
    <call id="12" ref="1" state="idle" ext="6" share="T"/>   
    <speaker state="off" vol="0"/>  
     <headset state="on" vol="0"/>   
    <handset state="onhook" vol="13"/>   
    <ringer state="on" vol="8"/>   
    <agent state="unavailable"/>  
    </spa-status>      
    


Rate this Article:
     

Add Your Comments


Name: *
Email Address:
Web Address:
   
  
 
 
   
Verification Code:
*
 

Details
Last Modified:Friday, July 16, 2010
Last Modified By: Administrator
Type: FIX
Article not rated yet.
Article has been viewed 416 times.
Options