Extension not found in context 'phones'

Asterisk Asterisk Support
#1

Hi

i have installed Asterisk on ubuntu on AMD machine

after successful installation of asterisk 1.8.8 i have also installed a soft phone Twinkle. I am running asterisk and twinkle on same machine.

here are the my config files

sip.conf
[general]
context=default
allowoverlap=no
bindport=5060
bindaddr=0.0.0.0
srvlookup=yes

[blaine]
type=friend
context=phones
host=dynamic

[billy]
type=friend
context=phones
host=dynamic

extensions.conf

[globals]

[general]
autofallthrough=yes

[default]
exten => s,1,Verbose(1|Unrouted call handler)
exten => s,n,Answer()
exten => s,n,Wait(1)
exten => s,n,Playback(tt-weasels)
exten => s,n,Hangup()

[incoming_calls]

[internal]
exten => s,1,Verbose(1|Echo test application)
exten => s,n,Echo()
exten => s,n,Hangup()

exten => 1000,1,Verbose(1|Extension 1000)
exten => 1000,n,Dial(SIP/billy,30)
exten => 1000,n,Hangup()

exten => 1002,1,Verbose(1|Extension 1002)
exten => 1002,n,Dial(SIP/blaine,30)
exten => 1002,n,Hangup()

[phones]
include => internal
include => default

any help is much appreciated… thank you

#2

Which extension is not found?

Also your dialplan contains syntax that shouldn’t parse properly with the version of Asterisk you claim to be using. “|” is no longer used as the parameter separator.

#3

Hi David ,

here is the exact message :

i tried both the extensions from billy and blaine

chan_sip.c:22147 handle_request_invite: Call from ‘billy’ (127.0.0.1:5062) to extension ‘1002’ rejected because extension not found in context ‘phones’.

chan_sip.c:22147 handle_request_invite: Call from ‘blaine’ (127.0.0.1:5061) to extension ‘1000’ rejected because extension not found in context ‘phones’.

could you please suggest the exact syntax to be parsed , i have removed “|” but no use

#4

You want to be using commas, not pipes. Asterisk probably isn’t parsing those extensions

Try and run dialplan show phones and you will see what Asterisk is loading and what it isn’t

#5

The error with the “|” characters won’t come into play until the dialplan is actually run. The load time parsing isn’t that thorough.