Obtaining support

Version 28 (Adrian Georgescu, 12/04/2012 12:29 pm)

1 1 Tijmen de Mes
h1. Obtaining/Requesting support
2 1 Tijmen de Mes
3 2 Tijmen de Mes
AG Projects provides support via its ticketing system available at: http://support.ag-projects.com
4 1 Tijmen de Mes
5 1 Tijmen de Mes
To open a ticket you must have a login account on AG Projects support system. You need a support contract from AG Projects before opening a ticket. If you already have a support contract and login account you can " create sub-accounts for your team members":https://mdns.sipthor.net/provisioning_mdns.phtml?1=1&service=customers%40sipthor&showAddForm=1.. Use the sub-accounts to login and open support tickets. The Operator must be able to provide remote access to equipment(s) where the problem occur and must provide remote hands and eyes at the facility when necessary.
6 1 Tijmen de Mes
7 1 Tijmen de Mes
The person that opens the ticket must have good understanding about how the platform works.
8 1 Tijmen de Mes
9 1 Tijmen de Mes
h2. How to Open a Ticket
10 1 Tijmen de Mes
11 1 Tijmen de Mes
In order to receive prompt and accurate support from AG Projects, please describe a single problem per ticket. Do not mix multiple problems in one ticket.
12 1 Tijmen de Mes
13 1 Tijmen de Mes
The ticket must contain minimum the following information:
14 1 Tijmen de Mes
15 1 Tijmen de Mes
# *What* is the problem, describe it as accurately as you can
16 1 Tijmen de Mes
# *Where* the problem occurs - specify the SIP Account, Internet Address, URL or the hostname of the machine that exhibit the problem. In case of failed calls, please specify the Call Id, see the Failed Calls section below
17 1 Tijmen de Mes
# *When* the problem happened, the date and time, if the problem is still in progress and how it can be reproduced (when possible)
18 1 Tijmen de Mes
19 1 Tijmen de Mes
To speed up the process, please paste relevant information from the syslog of the machine where the problem occurs.
20 1 Tijmen de Mes
21 1 Tijmen de Mes
h2. Failed Calls
22 1 Tijmen de Mes
23 28 Adrian Georgescu
If you have a problem with failed SIP sessions through the platform use CDRTool applicatio nfollow this procedure:
24 1 Tijmen de Mes
25 1 Tijmen de Mes
# Find the call detail record (a.k.a. CDR) of the failed session in CDRTool application. The CDR contains the SIP Call Id and links to the SIP trace and media trace of the session. Save the CDRTool query by giving it a name in the results screen.
26 1 Tijmen de Mes
# Locate the SIP session in /var/log/syslog of each machine involved (SIP Proxy, Call Control, Media Proxy, CDRTool rating engine). To locate the lines in syslog belonging to a session you can use grep command and the SIP Call Id learnt above as search key. Read the syslog above and below the found log lines they usually provide clues about the failure reason. Example:
27 17 Tijmen de Mes
# Open a ticket in AG Projects support system (see Requesting support section above) and provide the link to the failed session saved previously.
28 1 Tijmen de Mes
29 1 Tijmen de Mes
The CDRTool application for SIPThor Net runs at http://mdns.sipthor.net/CDRTool/
30 28 Adrian Georgescu
31 27 Adrian Georgescu
32 6 Tijmen de Mes
!cdrtool-call-search.png!
33 1 Tijmen de Mes
34 7 Tijmen de Mes
!cdrtool-search-results.png!
35 4 Tijmen de Mes
36 1 Tijmen de Mes
h2. SIP Trace
37 1 Tijmen de Mes
38 1 Tijmen de Mes
Each successful CDR has a SIP trace associated with it. The trace is available by clicking on the CDR id in the result screen of CDRTool search.
39 1 Tijmen de Mes
40 1 Tijmen de Mes
SIP trace can be turned on and off by controlling OpenSIPS:
41 1 Tijmen de Mes
42 16 Tijmen de Mes
<pre>
43 16 Tijmen de Mes
/etc/init.d/opensips siptrace-on
44 16 Tijmen de Mes
/etc/init.d/opensips siptrace-off
45 16 Tijmen de Mes
</pre>
46 1 Tijmen de Mes
47 18 Tijmen de Mes
!cdrtool-sip-trace.png!
48 1 Tijmen de Mes
49 24 Adrian Georgescu
The trace information is stored by default in opensips.sip&#95;trace table. Purging this table is a disc-access intensive operation during which the server will act slower than normal.  Purge operations must be done during a maintenance window with no SIP traffic. Do not purge the file using an SQL query that selects by date, such a query will take long time to execute on a large table, during such query the server cannot access the database anymore.
50 1 Tijmen de Mes
51 1 Tijmen de Mes
h2. Media Trace
52 1 Tijmen de Mes
53 9 Tijmen de Mes
Each successful SIP session has information about the RTP media associated with it. The trace is available by clicking on the CDR id in the result screen of CDRTool search. 
54 9 Tijmen de Mes
55 20 Adrian Georgescu
!cdrtool-media-trace.png!
56 1 Tijmen de Mes
57 1 Tijmen de Mes
h2. DNS Lookups
58 1 Tijmen de Mes
59 1 Tijmen de Mes
Use dig command in a UNIX console to check if the DNS servers part of the platform are responding to queries.
60 1 Tijmen de Mes
61 1 Tijmen de Mes
h2. Syslog
62 1 Tijmen de Mes
63 1 Tijmen de Mes
All platform software log relevant messages to /var/log/syslog and optional additional files. Please always monitor these files when searching or troubleshooting a problem.
64 1 Tijmen de Mes
65 1 Tijmen de Mes
h2. Network Sniffers
66 1 Tijmen de Mes
67 1 Tijmen de Mes
If the problem is not captured by the high-level tools described above use:
68 1 Tijmen de Mes
69 19 Tijmen de Mes
# ngrep 
70 1 Tijmen de Mes
# tcpdump
71 1 Tijmen de Mes
72 1 Tijmen de Mes
to isolate the network traffic in question.