[Kamailio-Users] Unable to lookup host in c= line,

[Tincho ylm]

Thanks a LOT!!!

I have solved it!!

 if (t_check_status("487|486")) {
                        rewritehostport("200.xx.xx.xx:5060");
                        append_branch();
                        xlog("L_INFO","---> To Voicemail...\n");
                        setflag(10);
                        route(1);   <---------- t_relay();
                        exit;

That was the problem.

2009/9/24 Daniel-Constantin Mierla <miconda at gmail.com>:
> Hello,
>
> On 23.09.2009 17:58 Uhr, Tincho ylm wrote:
>>
>> Hi all!
>>
>> I'm trying to make a realtime environment openser-asterisk. At this
>> moment, everything is working fine but I have problems with VM
>> feature.
>> What I'm doing is:
>>
>> A call B
>> If B is busy and returns 486
>> Openser send this to Asterisk.
>>
>> failure_route[1] {
>>        if(!t_was_cancelled()) {
>>                if (t_check_status("487|486")) {
>>                        rewritehostport("200.xx.xx.xx:5060");
>>                        append_branch();
>>                        xlog("L_INFO","---> To Voicemail...\n");
>>                        setflag(10);
>>                        route(1);
>>                        exit;
>>                }
>>                if (isbflagset(6) || isflagset(5)) {
>>                        unforce_rtp_proxy();
>>                }
>>        }
>> }
>>
>> Asterisk cant handle it because this error:
>>
>> chan_sip.c:5121 process_sdp: Unable to lookup host in c= line, 'IN IP4
>> 200.xx.xx.xx200.xx.xx.xx'
>> chan_sip.c:5121 process_sdp: Unable to lookup host in c= line, 'IN IP4
>> 200.xx.xx.xx200.xx.xx.xx'
>> chan_sip.c:5121 process_sdp: Unable to lookup host in c= line, 'IN IP4
>> 200.xx.xx.xx200.xx.xx.xx'
>>
>> I'm using:
>> Kamailio 1.4.4
>> Rtpproxy
>> Asterisk 1.4.22
>>
>> Is it a rtpproxy issue? it can fix it?
>>
>> If I make a ethereal capture, I can see in the MESSAGE BODY this:
>>
>> connection inrfomation (c): IN IP4 200.xx.xx.xx200.xx.xx.xx
>>
>> What can I do?
>>
>>
>
> you have a problem in your config file -- you call twice force_rtp_proxy(0.
> Check the logic, probably from failure route you go again through another
> route where force_rtp_proxy() is executed -- you must avoid the second call
> of it.
>
> Cheers,
> Daniel
>
> --
> Daniel-Constantin Mierla
> * http://www.asipto.com/
>
>