Jump to content

Tips to help diagnose ringing no answer


andrewgroup
 Share

Recommended Posts

A new install (black new version) , left with ZERO logging, we had to remotely reset the system and it returned to answering incoming calls. What would be the best settings on the logging that might capture something to indicate the failure?

 

 

Currently running the following version.

 

Version: 2.1.6.2448 (Linux)

License Status: Appliance Key

License Duration: Permanent

Additional license information: Extensions: 10/32 Accounts: 22/40

Working Directory: /pbx

IP Addresses: eth2 192.168.1.99 192.168.1.0 255.255.255.0

eth1 1.1.1.1 1.1.1.0 255.255.255.0

lo 127.0.0.1 127.0.0.0 255.0.0.0

default 192.168.1.99

 

MAC Addresses: 00191568404A 00191568404B

Calls: 9/3 (CDR: 12) 0/0 Calls

SIP packet statistics: Tx: 706 Rx: 706

Emails: Successful sent: 0 Unsuccessful attempts: 0

Uptime: 0 01:00:42 (3950 4287808-0) WAV cache: 0

Media CPU Usage: 100%

0%

0 24

Link to comment
Share on other sites

If you can, use an SNMP tool to poll the PBX for data like how many calls are on. If the PBX does not respond, there is trouble going on.

 

It is *not* a good idea to stress the system with lots ot http/https requests to see if it is (still) responding. SNMP is very lightweight and has practically no impact on the operation.

Link to comment
Share on other sites

If you can, use an SNMP tool to poll the PBX for data like how many calls are on. If the PBX does not respond, there is trouble going on.

 

No Problem is http://wiki.pbxnsip.com/index.php/SNMP the full and complete MIB?

 

This original post had an odd occurance with it too. Failed to mention that, but I will now. The site has CABLE static IP and that remote location can dial 555 and this creates a SIP trunk to the main office back door AA basically a way fo the remote office o make toll free calls to HQ.

 

HQ experienced a FAILED Switch, thus killing the PBX for a bit, and we saw a call in the call log in the remote office trying to make a trunk call. We'll duplicate this in the LAB and confirm as this might just be coincident.

Link to comment
Share on other sites

No Problem is http://wiki.pbxnsip.com/index.php/SNMP the full and complete MIB?

 

So far yes. 2.2 will also add a memory sensor (number 12), but is not released yet.

 

HQ experienced a FAILED Switch, thus killing the PBX for a bit, and we saw a call in the call log in the remote office trying to make a trunk call.

 

Ouch. Network equipment like switches and routers are also not bug free. We have to keep this in mind when tracking down problems.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...