[asterisk-users] asterisk meetme invalid extension

[Danny Nicholas]

  _____  

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of satish patel
Sent: Wednesday, April 06, 2011 4:47 PM
To: asterisk-users
Subject: Re: [asterisk-users] asterisk meetme invalid extension

 

i did and its not working here is console output. We have 8910-8920  meetme
conf room.  below i am dialing 8991 for test invalid and its not working.. 


Packet timed out after 32000ms with no response
  == Using SIP RTP CoS mark 5
    -- Executing [7580 at from-sip:1] Goto("SIP/7527-00000030",
"ivr-meetme,s,1") in new stack
    -- Goto (ivr-meetme,s,1)
    -- Executing [s at ivr-meetme:1] Answer("SIP/7527-00000030", "") in new
stack
    -- Executing [s at ivr-meetme:2] Wait("SIP/7527-00000030", "1") in new
stack
    -- Executing [s at ivr-meetme:3] BackGround("SIP/7527-00000030",
"conf-getconfno") in new stack
    -- <SIP/7527-00000030> Playing 'conf-getconfno.ulaw' (language 'en')
    -- Executing [s at ivr-meetme:4] WaitExten("SIP/7527-00000030", "20") in
new stack
  == CDR updated on SIP/7527-00000030
    -- Executing [8991 at ivr-meetme:1] MeetMe("SIP/7527-00000030", "8991,cMp")
in new stack
  == Parsing '/etc/asterisk/meetme.conf':   == Found
  == Spawn extension (ivr-meetme, 8991, 1) exited non-zero on
'SIP/7527-00000030'
shirley*CLI>




[Danny Nicholas] 

As I stated in my earlier reply, _89XX indicates that 8900 thru 8999 are
acceptable.  Therefore you should either change _89XX to _89[12]X or to be
really accurate make it two lines _891X and _8920.  Alternatively you could
use some Gotoif's but why code when the dialplan does it for you?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110406/69cbde39/attachment.htm>