<div class="gmail_quote">On Tue, Mar 29, 2011 at 1:25 PM, Jeremy Kister <span dir="ltr"><<a href="mailto:asterisk-01@jeremykister.com">asterisk-01@jeremykister.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 3/29/2011 1:56 PM, Sherwood McGowan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[mypeer](peer)<br>
host=10.0.138.226<br>
defaultuser=2155551941<br>
fromuser=2155551941<br>
md5secret=023f30a320a5781e8ffd1af9888012af<br>
incominglimit=10<br>
</blockquote></blockquote>
<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
IIRC, you need to define the fromuser in the peer in order for the<br>
qualify checks (options packets) to contain the user you want<br>
</blockquote>
<br></div>
uhm, didn't I ?<br clear="all"></blockquote></div><br>It looks like you did to me. Is it just OPTIONS packets that are showing the wrong fromuser field? In other words, when you send call traffic over this peer, does it properly create the SIP packets? For some reason, I'm thinking this is "just the way it is", but someone closer to the the actual sip development may be able to better tell you. Perhaps open a ticket on the bug tracker?<br>
<br>-- <br>Thanks,<br>--Warren Selby, dCAP<br><a href="http://www.selbytech.com" target="_blank">http://www.selbytech.com</a><br>