[asterisk-users] Realtime problem host='dynamic' in 1.2.26.1

[Torbjörn Abrahamsson]

Yes, it does... This is not a problem of usage. This mail should 
probably have been sent to -dev instead, as it clearly is a bug.

If you take a look at the link I provided you will see that this is 
indeed a bug, and it has been fixed in 1.4 branch in 1.4.17. The problem 
is that 1.2 is in "security fixes only"-mode, and thereby this should 
not be fixed. My question is, that as this is a bug that occurs as a 
result of a broken security fix, will a fix for this be released anyway?

I have backported the changes to chan_sip.c 1.4-fix for this to 
1.2.26.1, so I do have a working solution but I hope to be able to use 
an "official" release.

// T


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