Jan 23 09:02:07 DEBUG[2236] res_config_mysql.c: MySQL RealTime: Retrieve<br>SQL: SELECT * FROM sippeers WHERE name = '989800-out' AND host = 'dynamic'<br><br>Quite obvious .. doest sippeers have that row ?<br>
<br><div class="gmail_quote">On Jan 24, 2008 6:04 PM, Torbjörn Abrahamsson <<a href="mailto:torbjorn.abrahamsson@gmail.com">torbjorn.abrahamsson@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Developers and maintainers, any information?<br><font color="#888888"><br>// T<br></font><div><div></div><div class="Wj3C7c"><br>Torbjörn Abrahamsson wrote:<br>> Hello!<br>><br>> We are using the 1.2 branch, and upgraded to
<a href="http://1.2.26.1" target="_blank">1.2.26.1</a>. We ran into some<br>> problems when using realtime for peers. We connect the PBX to a sip peer<br>> at an ITSP, and when we try to dial the peer we get:<br>>
<br>> Jan 23 09:02:07 VERBOSE[2236] logger.c: -- Executing<br>> Dial("SIP/dev02-08c36f28", "SIP/3246@989800-out||W") in new stack<br>> Jan 23 09:02:07 DEBUG[2236] res_config_mysql.c: MySQL RealTime:
<br>> Everything is fine.<br>> Jan 23 09:02:07 DEBUG[2236] res_config_mysql.c: MySQL RealTime: Retrieve<br>> SQL: SELECT * FROM sippeers WHERE name = '989800-out' AND host = 'dynamic'<br>> Jan 23 09:02:07 WARNING[2236] chan_sip.c: No such host: 989800-out
<br>> Jan 23 09:02:07 NOTICE[2236] app_dial.c: Unable to create channel of<br>> type 'SIP' (cause 3 - No route to destination)<br>> Jan 23 09:02:07 VERBOSE[2236] logger.c: == Everyone is busy/congested<br>
> at this time (1:0/0/1)<br>> Jan 23 09:02:07 DEBUG[2236] app_dial.c: Exiting with DIALSTATUS=CHANUNAVAIL.<br>><br>> I looked in the archives and found this thread:<br>><br>> <a href="http://lists.digium.com/pipermail/asterisk-users/2007-December/202616.html" target="_blank">
http://lists.digium.com/pipermail/asterisk-users/2007-December/202616.html</a><br>><br>> Here the same problem is discussed for the 1.4 branch, and the result is<br>> that the problem should be fixed. But this is still a problem in
1.2 branch.<br>><br>> Will this be corrected in a new release, or is this not considered a<br>> security fix and hence ignored? Actually isn't this a fix for a security<br>> fix...<br>><br>> BR,<br>> Torbjörn Abrahamsson
<br>><br>><br>><br>><br>><br>><br>><br>> _______________________________________________<br>> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.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" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users
</a><br>><br>><br><br>_______________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.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" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></div></div></blockquote></div>
<br>