Some calls not working

[emebit]

Since yesterday we have had occasional problems with both incoming and outgoing calls. The problem happens with multiple phone/numbers.

outgoing:
- pickup handset
- dial number
- then nothing
- hangup/redial will work

incoming:
- phone rings
- answer, but no one there
- when the calling party does get through they often
report that they had trouble reaching us. No busy
signals or anything like that.

I don't see any alarms or anything else out of the ordinary. When I have tried to get it to fail (while tracing an extension) it always works.

All these calls should be on our ISDN trunk group.

Any suggestions?

 

[orypecos]

IF u do 'list measurement ds1 xxxx log today' do u have errors?

Da-vi'do
P.S. For the best response to a question, read FAQ222-2244. Also give the type & version of your voice mail & pbx & preview your post to make sure it is complete & understandable. Please answer all questions so that I may have the info to assist you. Leaving a post on how you fixed the problem will also be appreciated.

 

[emebit]

I could not run that exact command, but I did do

list measurements ds1 log xxxx

I assumed the xxxx was to be replaced with the port corresponding to each trunk.

All fields for all time periods on all ISDN trunks were 0.

System: G3csiV9 Software Version: G3V9i.02.0.033.2

 

[orypecos]

Did u put in the 'port number' or the 'board number'?
It should be the 'board number' on the trunk that is in trouble.
U can do it for yesterday too.
Do 'status synch' , is the syn on a isdn board or the toneclock.
If it is on the tone clock, it needs to be on a t=1 board.

 

[emebit]

I used the port numbers e.g. 01A1001 that show up when you do a 'display trunk-group xxxx'. If that is not it, I'll need to know how to determine what is the correct board number.

'status sync' gave me...

                Stratum Level: 4
             Maintenance Name: UDS1-BD     Physical Location: 01A10
         Switching Capability: Enabled                         
Excessive Reference Switching:

but is doesn't mean anything to me.

 

[orypecos]

Use the command "list measurements ds1 log 01A10" and see if there are any errors. Also look at "list measurements ds1 log 01A10 yesterday". I think that is a valid command.
The 'synch' looks ok.
When a call comes in, status the station and see if it is connected to board a10.
U might want to look at the other trunks measurements and see if they have errors just in case they are coming in on another trunk.
Did u just get another provider for that trunk?
What changed right before u started having these problems?

 

[emebit]

Did the "list measurements ds1 log 01A10" and there were no errors. I did see a "Connected Ports: 01A1011" when doing a "status station xxxx" but that was on a working connection. Trying to catch one that doesn't work could prove challenging.

The only other trunk group we have is a 'co' type. That "list measurement ds1 log xxxxx" doesn't work for that. The only thing using that group should be our main numbers and there are not reports of problems with that.

No providers changed. The only recent change involving having some 800 numbers mapped to different numbers and some other 800 numbers terminated.

 

[orypecos]

The "status station xxxx" was to find out it U are looking at the correct trunk. U can also do 'display errors' and put in the board number or trunk number and then follow the maintenance books to see what the errors indicate.

 

[sjforcum]

Where are you located? I'm in CT and we're experincing the same thing...it's related to a Gas explosion in the subway which happened last night. It affected the POP for a lot of LD carriers (ours is Paetec).

I would contact your LD carrier.

 

[sjforcum]

Also I forgot to mention the explosion happened in Boston last night around 6PM.

it's on the front page of

http://www.boston.com

 

[emebit]

I just discovered the 'Error List:' field under in the 'display errors' screen. If I change it from the default of 'active-alarms' to 'errors' I got all sorts of stuff. Limiting the time window to the past 15 days or so I got...

Port      Mtce     Alt     Err   Aux     First       Last      Err Err Rt/ Al Ac
          Name     Name    Type  Data    Occur       Occur     Cnt Rt  Hr  St  
1         ISDN-SGR         1793        11/12/00:49 01/28/00:49 2   0   0   n  n
01A1024   SYS-LINK PRI     1025        09/24/00:55 01/28/00:49 3   0   0   n  n
01A0505   CO-TRK   02/31   3073  57376 08/05/13:54 01/31/15:35 27  0   0   n  n
01A0508   CO-TRK   02/34   2817  57360 08/14/01:33 02/02/01:04 4   0   0   n  n
01B0715   DIG-LINE 3468    1537  40968 08/04/14:39 01/31/12:44 4   0   0   n  n
01A       TDM-CLK          513   16644 08/05/01:01 02/03/01:01 41  0   0   n  n
01A0407   DIG-LINE         3841  0     09/22/13:44 02/03/10:23 255 0   0   n  n
01A0611   DIG-LINE         3841  0     09/22/14:59 02/03/11:07 255 0   0   n  n
01A0822   AN-LN-PT 3402    513         11/03/01:13 01/31/01:13 9   0   0   n  n
01B0108   AN-LN-PT 3699    513         01/07/01:09 02/03/11:06 255 0   3   a  y
01B0107   AN-LN-PT 3411    1     40975 01/19/15:46 01/29/06:42 25  0   0   n  n
01A0608   DIG-LINE         2305  32770 01/27/11:05 01/27/11:06 5   300 0   n  y
01B0724   DIG-LINE 3407    1537  40968 02/01/13:39 02/01/13:39 1   0   0   n  n

Now to figure out what this all means.


BTW, I am located in central MD. So I doubt a gas explosion in CT is at fault here.

 

[orypecos]

Do the same 'display errors' and put in default of 'active-alarms' to 'errors' , but then put the 01a10 board down near the bottom to limit your errors.