Handsets Shows Busy after 4 Days

AndyMoore

Joined
Jun 27, 2007
Messages
8
Likes
0
Points
0
#1
Guys,
The following is the status of the handset on an inbound call.

dialparties.agi: priority is 1
dialparties.agi: Caller ID name is '08703501284' number is '08703501284'
dialparties.agi: Methodology of ring is 'none'
-- dialparties.agi: Added extension 5141 to extension map
-- dialparties.agi: Extension 5141 cf is disabled
-- dialparties.agi: Extension 5141 do not disturb is disabled
dialparties.agi: Extension 5141 has ExtensionState: 16
-- dialparties.agi: Checking CW and CFB status for extension 5141
dialparties.agi: Extension 5141 is not available to be called
dialparties.agi: Extension 5141 has call waiting disabled

You will see the extension state as 16 (busy), the call goes direct to voicemail.

There are no CFWd's on the extension.

Are restart of Asterisk resolves the issue.

This platform is 0.84 Beta 1, I will upgrade to the full release but the switch is in test at the moment with a client.

Any ideas?

Andy
 

adminad

Joined
Apr 29, 2010
Messages
150
Likes
0
Points
0
#2
Maybe is an asterisk bug. Please send the output of the following CLI command: "core show hints"

Maybe this is because there is an asterisk bug that put the extensions on HOLD after a call transfer or some weird situations.
 

AndyMoore

Joined
Jun 27, 2007
Messages
8
Likes
0
Points
0
#3
Hi,
Output of core show hints.

-= Registered Asterisk Dial Plan Hints =-
5141@ext-local : SIP/5141 State:Idle Watchers 0
5140@ext-local : SIP/5140 State:Idle Watchers 0
5062@ext-local : SIP/5062 State:Idle Watchers 0
5061@ext-local : SIP/5061 State:Idle Watchers 0
5060@ext-local : SIP/5060 State:Idle Watchers 0
104@ext-local : SIP/104 State:Idle Watchers 0
103@ext-local : SIP/103 State:Idle Watchers 0
102@ext-local : SIP/102 State:Idle Watchers 0
101@ext-local : SIP/101 State:Unavailable Watchers 0
100@ext-local : SIP/100 State:Idle Watchers 0

The PBX has been upgraded to the latested 0.84 release and Asterisk 1.4.6

The issue is not so apparent now but, still occurs on call transfers.

Andy
 

jeffrey

Joined
Jul 9, 2007
Messages
4
Likes
0
Points
0
#4
I have the identical problem to this.

Any ideas guys?
 

lek

Guest
#5

jeffrey

Joined
Jul 9, 2007
Messages
4
Likes
0
Points
0
#6
Hey guys,

Saw the resolution to this post on the digium site. If anyone could tell me what it means and what I have to do I would be so happy.

I'm a genuine antique, so please type slowly!
 

AndyMoore

Joined
Jun 27, 2007
Messages
8
Likes
0
Points
0
#7
Hey,
The line you are referring to is:

notifyhold = no

Default is usually yes.

Basically, this is to do with endpoint presence, so if you have a handset watching hints, i.e. Handset Busy, on Hold etc.. This line will notify for on hold status, turning it off removes the problem but you may in the future want to use the presence features of Asterisk.

Andy
 

jeffrey

Joined
Jul 9, 2007
Messages
4
Likes
0
Points
0
#8
Great answer, but where does this line go?
 

AndyMoore

Joined
Jun 27, 2007
Messages
8
Likes
0
Points
0
#9
Sorry,
In sip.conf under general. Here is a snip.

[general]

bindport = 5060 ; Port to bind to (SIP is 5060)
bindaddr = 0.0.0.0 ; Address to bind to (all addresses on machine)
disallow = all
allow = ulaw
allow = alaw
allow = g729
; If you need to answer unauthenticated calls, you should change this
; next line to 'from-trunk', rather than 'from-sip-external'.
; You'll know this is happening if when you call in you get a message
; saying "The number you have dialed is not in service. Please check the
; number and try again."
context = from-sip-external ; Send unknown SIP callers to this context
callerid = Unknown
tos=0x68

; Agregado para soporte de Asterisk 1.4 - PSS 18-May-07
notifyhold = no

The line you want is above and it goes into [General] section.
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,886
Members
17,563
Latest member
dineshr
Top