Mailing List Archive

Suddenly can't make calls (it sound busy)
Just last week I was able to make calls through VoIP,
but suddenly I can't. If I dial the call is made but then a few seconds later
(also I can't hear the call progress indicator) sounds as if it was busy.
However, the other peer can make calls to my router.

My config (relevant parts only):
- - - - - - - - - - - - - - - - - -
!
voice-port 1
!
...
!
dial-peer voice 10 pots
destination-pattern 4010
port 1
!
...
!
dial-peer voice 100 voip
tone ringback alert-no-PI
destination-pattern 50..
session target ipv4:<OtherHostIP>
!
...
- - - - - - - - - - - - - - - - - -


What I've been able to debug so far:
- - - - - - - - - - - - - - - - - -
# show dialplan number 5010

VoiceOverIpPeer100
peer type = voice, information type = voice,
description = `',
tag = 100, destination-pattern = `50..',
...
translation-profile = `'
disconnect-cause = `no-service'
type = voip, session-target = `ipv4:<OtherHostIP>',
...
Last Disconnect Cause is "1B ",
Last Disconnect Text is "destination out of order (27)",
Last Setup Time = 2496017.
Matched: 5010 Digits: 2
Target: ipv4:<OtherHostIP>
- - - - - - - - - - - - - - - - - -

I was reading from
http://www.cisco.com/warp/public/129/isdn_disc_code.html
that there is a way of detecting the "Cause Code Origination Point"
from the output of the command:
# debug isdn q931

but I can't find any similar command for my situation. I've tried with
debug pots ringer
debug dialpeer
but the don't issue the 'Cause i =' output (used in the url above)

Does anybody know the equivalent command or any other tip that can help
me to debug and resolve my problem?

Thanks a lot in advance for your help
Highest Regards,

Ed
Re: Suddenly can't make calls (it sound busy) [ In reply to ]
> Have you checked your peer? From the last disconnect text, it seems to
> point to a problem on the peer (e.g., their POTS is not working).
>
> Regards, Neil

You mean like a physical layer or data link layer failure at the remote user,
user equipment off-line, etc.?
RE: Suddenly can't make calls (it sound busy) [ In reply to ]
Did you look at sh process? We have had some issues kinda like that and
the router is running 50%+ process. I think It's the blaster worm, but
I'm not sure. Anyone else seen this?

-scott

-----Original Message-----
From: MC_Vai [mailto:estoy@ver.megared.net.mx]
Sent: Tuesday, August 26, 2003 7:12 PM
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Suddenly can't make calls (it sound busy)



> Have you checked your peer? From the last disconnect text, it seems
to
> point to a problem on the peer (e.g., their POTS is not working).
>
> Regards, Neil

You mean like a physical layer or data link layer failure at the remote
user,
user equipment off-line, etc.?
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip