[invalid]<br>> exten => _X!,1,Answer()<br>> exten => _X!,2,Background(pbx-invalid)<br><br>Are you sure that your invalid context is correctly written?<br><br>I've never heard about this pattern match _X!<br>As far as i know the wild card is the "."
<br>So your invalid context should be:<br><br> [invalid]<br>exten => _X.,1,Answer()<br>
exten => _X.,2,Background(pbx-invalid)<br><br>This may be the cause....<br><br>Hope it helps.<br><br><br><div><span class="gmail_quote">On 9/29/06, <b class="gmail_sendername">Brian Candler</b> <<a href="mailto:B.Candler@pobox.com">
B.Candler@pobox.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Fri, Sep 29, 2006 at 07:49:00PM +0200, Michael Neuhauser wrote:
<br>> The order of include statements is important in 1.2, I don't know if<br>> this still holds for trunk/1.4. Could you please try to include the<br>> 'invalid' context as the last one (i.e., AFTER "include => test", not
<br>> before) in both internal and from-sip and then test again?<br><br>Yes, this works - both contexts now behave the same.<br><br>But what I don't understand is, why it worked in one context but not in the<br>other, when both just included the same four other contexts in the same
<br>order. Is the context merging non-deterministic? Or is it somehow sensitive<br>to whether the incoming call came from zaptel or SIP?<br><br>Regards,<br><br>Brian.<br>_______________________________________________<br>
--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">
http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></blockquote></div><br><br clear="all"><br>-- <br>Com os melhores cumprimentos,<br><br>Marco Mouta