Oh, you are *not* going to like this, but....<br><br>you have a few different paths:<br><br>1. If the dialplan stuff is not really a memory corruption, but some sort of unplanned,<br> but maybe accidentally programmed thing, either by you or something in the asterisk<br>
code, then:<br><br>a. compile asterisk for debug. You can get in the menuselect stuff and make sure<br> the debug compile options are turned on. Install it.<br>b. Shut down asterisk<br>c. fire it back up, under gdb:<br>
<br> gdb <full path to asterisk><br> br ast_context_remove_extension_callerid2<br> comm 1 <br> where<br> c<br> end<br> run <normal arguments to asterisk><br><br>Then use asterisk as normal and wait for the problem to re-occur. Look to see if any<br>
calls to ast_context_remove_extension_callerid2 occurred (they will occur with dial reloads-- lots of them).<br>You'll have to search carefully! The gdb messages could be buried in your console output.<br><br>If the problem reoccurs, but you didn't see any calls to ast_context_remove_extension_callerid2,<br>
then it could be assumed that you are suffering some sort of memory corruption.<br>Where it dies, or things start looking strange, may not indicate where or why the corruption is<br>happening. In such a case, it really gets tricky to debug. Then we might resort to <br>
stuff like dmalloc, and others, to help spot where/when corruption occurs. Let's cross that<br>bridge if we come to it.<br><br>murf<br><br><br><div class="gmail_quote">On Tue, Apr 5, 2011 at 7:30 AM, Jerry Geis <span dir="ltr"><<a href="mailto:geisj@pagestation.com">geisj@pagestation.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5">Jerry Geis wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Steve Murphy wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Idea:<br>
<br>
If something is corrupting your dialplan, then this should<br>
reveal the extent of the corruption:<br>
<br>
You might, when the system is working properly, do a:<br>
<br>
asterisk -rx "dialplan show" > somefile1<br>
<br>
and then, when you are having problems, do a:<br>
<br>
asterisk -rx "dialplan show" > somefile2<br>
diff -u somefile1 somefile2<br>
<br>
and see if this reveals anything juicy.<br>
<br>
murf<br>
<br>
</blockquote>
<br>
Steve,<br>
<br>
That is a great idea. I did that the first time it happened. I dumped the dialplan, then I restarted<br>
and dumped again. it was the same. Being the first time I thought it was just a fluke but now it<br>
has happened a couple of times. I have not been able to narrow anything down.<br>
<br>
Thanks,<br>
<br>
jerry<br>
<br>
</blockquote></div></div>
Steve,<br>
<br>
perhaps I did something wrong the first time. As I just got the error again. I dumped the dialplan and my section:<div class="im"><br>
<br>
[ Context 'smvoice-mediaport' created by 'pbx_config' ]<br>
<br></div>
is empty.<br>
<br>
when I restart and dump again.<div class="im"><br>
<br>
[ Context 'smvoice-mediaport' created by 'pbx_config' ]<br>
'1105' => 1. Goto(smvoice-mediaport-public-address,s,1) [pbx_config]<br></div>
'mediaport_direct' => 1. Goto(smvoice-mediaport-public-address,s,1) [pbx_config]<br>
'public_address' => 1. Goto(smvoice-mediaport-public-address,s,1) [pbx_config]<br>
<br>
I have the correct data.<br>
<br>
The only thing I have in the dialplan for this box is:<div class="im"><br>
[smvoice-mediaport-public-address]<br>
exten => s,1,System(/home/silentm/bin/smfunctions -stop)<br>
exten => s,n,Playback(beep)<br>
exten => s,n,Dial(Console/dsp)<br>
exten => s,n,Hangup<br>
exten => h,1,System(/home/silentm/bin/smfunctions -start)<br>
<br></div>
Can a system call be removing stuff from the dialplan?<br>
<br>
What next?<br></blockquote><div>Oh, you are *not* going to like this, but....<br>
<br>
you have a few different paths:<br>
<br>
1. If the dialplan stuff is not really a memory corruption, but some sort of unplanned,<br>
but maybe accidentally programmed thing, either by you or something in the asterisk<br>
code, then:<br>
<br>
a. compile asterisk for debug. You can get in the menuselect stuff and make sure<br>
the debug compile options are turned on. Install it.<br>
b. Shut down asterisk<br>
c. fire it back up, under gdb:<br>
<br>
gdb <full path to asterisk><br>
br ast_context_remove_extension_callerid2<br>
comm 1 <br>
where<br>
c<br>
end<br>
run <normal arguments to asterisk><br>
<br>
Then use asterisk as normal and wait for the problem to re-occur. Look to see if any<br>
calls to ast_context_remove_extension_callerid2 occurred (they will occur with dial reloads-- lots of them).<br>
You'll have to search carefully! The gdb messages could be buried in your console output.<br>
<br>
If the problem reoccurs, but you didn't see any calls to ast_context_remove_extension_callerid2,<br>
then it could be assumed that you are suffering some sort of memory corruption.<br>
Where it dies, or things start looking strange, may not indicate where or why the corruption is<br>
happening. In such a case, it really gets tricky to debug. Then we might resort to <br>
stuff like dmalloc, and others, to help spot where/when corruption occurs. Let's cross that<br>
bridge if we come to it.<br>
<br>
murf<br>
<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><font color="#888888">
<br>
Jerry<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br><div><span style="font-size: 13.3px; font-family: Verdana,Arial,Helvetica,sans-serif;"><div style="margin: 0pt 0pt 8px;"><p style="margin: 0pt;"><span style="font-family: comic sans ms,sans-serif; font-size: medium;">Steve Murphy</span></p>
<p style="margin: 0pt;"><span style="font-family: comic sans ms,sans-serif; font-size: medium;">ParseTree Corporation<br></span></p><br></div></span></div><div><span style="font-size: 13.3px; font-family: Verdana,Arial,Helvetica,sans-serif;"><img src="http://s.wisestamp.com/pixel.png?p=mozilla&v=2.0.3&t=1287885769470&u=6672444&e=5113" width="1" height="1"></span></div>
<br>