...
| Code Block |
|---|
| language | bash |
|---|
| title | Restart MySQL service |
|---|
|
[root@ha1 ~]# service mysqld stop
Stopping mysqld: [ OK ]
[root@ha1 ~]# service mysqld start
Starting mysqld: [ OK ] |
6.3.4 Asterisk
The Asterisk service is splitted into two different sub-services which are the SIP service for PrivateGSM Users and the SIP Trunk to perform end-to-site calls directed to a local PBX. First we assure that the main process is alive:
| Code Block |
|---|
| language | bash |
|---|
| title | Check Asterisk status |
|---|
|
[root@ha1 ~]# service asterisk status
asterisk (pid 16418) is running... |
Then we try to connect to the Asterisk command line interface:
| Code Block |
|---|
| language | bash |
|---|
| title | Connect to Asterisk CLI |
|---|
|
[root@ha1 ~]# rasterisk -rvvv
Asterisk 1.8.9.1, Copyright (C) 1999 - 2011 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
== Parsing '/etc/asterisk/asterisk.conf': == Found
== Parsing '/data/etc/asterisk/maxcalls.conf': == Found
Setting max files open to 65536
[Apr 13 12:49:20] Connected to Asterisk 1.8.9.1 currently running on ha1 (pid = 16418) |
inside the console we raise the information level:
| Code Block |
|---|
| language | bash |
|---|
| title | Raise the Asterisk CLI information level |
|---|
|
ha1*CLI> core set debug 99
Core debug was 0 and is now 99
ha1*CLI> core set verbose 99
Verbosity was 0 and is now 99
ha1*CLI> |
This would notice us as soon as any trouble arises. The particular troubleshooting about Asterisk can't be covered in this manual and we ask you to refer to the specific Asterisk documentation (http://www.asterisk.org).
If the status check returns an error such as:
| Code Block |
|---|
| language | bash |
|---|
| title | Asterisk bad status |
|---|
|
[root@ha1 ~]# service asterisk status
asterisk is stopped |
Then you can try to run the Asterisk daemon manually, having particular attention to the console error messages if any:
| Code Block |
|---|
| language | bash |
|---|
| title | Restart Asterisk service |
|---|
|
[root@ha1 ~]# service asterisk start
Starting asterisk: Setting max files open to 65536
[ OK ]
[root@ha1 ~]# service asterisk status
asterisk (pid 31716) is running... |
| Tip |
|---|
If you want to exit the Asterisk CLI, just insert the "quit" command and press Enter button |
6.3.5 Asterisk Trunk
| Note |
|---|
The checks about Asterisk's trunk(s) have to be performed only in case of sip trunk configurations. Refer to 2.5 Sip Trunk(s) configuration. |
If you have a Trunk configured, then you can go further. From the Asterisk CLI (refer to the previous paragraph) you can perform a check of the trunk registration:
| Code Block |
|---|
| language | bash |
|---|
| title | check the trunk registration status |
|---|
|
ha1*CLI> sip show registry
Host dnsmgr Username Refresh State Reg.Time
sip.messagenet.it:5060 N xxxxxxx 105 Registered Fri, 13 Apr 2012 16:52:21 |
In the case shown above we have a correct trunk registration. Else the output is empty, so you have to check your trunk settings.
| Warning |
|---|
Remember that sip Trunks are UDP and this can trigger firewall settings |