[OpenSIPS-Users] What is protocol/port mismatch?

[Bogdan-Andrei Iancu]

Hi Brian,

Asking as the trace you previously sent me was showing a crash in the 
uac_replace_xxx() function, because of a bogus "display" pointer. I 
wanted to see how you call the functions to see if they try to change 
the display part or not. And it looks it doesn't, so the "display" param 
should be NULL.

Is the crash reproducible ?

Regards,
Bogdan

opensipslist at encambio.com wrote:
> Hello Bogdan,
>
> An jeu., févr 11, 2010, Bogdan-Andrei Iancu schrieb:
>   
>> opensipslist at encambio.com wrote:
>>     
>>> I should tell you that I've recompiled OpenSIPS since the crash.
>>> The changes are unrelated to the core or uac module so there's no
>>> problem, however it might be that the core you've asked to study
>>> reports memory locations that don't match the new running OpenSIPS.
>>>
>>> Also, I've changed the route script to use subst() from textops
>>> instead of uac_replace_(from|to) to avoid getting this crash. I'm
>>> still not convinced 100% that it's in replace.c, because it seemed
>>> to me that uac_replace_(from|to) sometimes worked fine.
>>>
>>>       
>> How do you invoke the uac_replace_xxx() which crashes?
>>
>>     
> I had:
>
>   uac_replace_to("sip:$tU@$avp(s:realm)");
>   uac_replace_from("sip:$avp(s:user)@$fd");
>
> Now I'm using:
>
>   subst('/^(To:[^:]+:)[^@]+@[^>;]+/\1$rU@$avp(s:realm)/');
>   subst('/^(From:[^:]+):[^@]+@[^>;]+/\1:$avp(s:user)@$avp(s:realm)/');
>
> ...but I can't remember anymore the reason that made me think the
> uac_replace_*** functions were at fault for crashes. If you're
> interested then I can diagnose this further. In that case please
> suggest a course of testing, how you recommend I figure this out.
>
> Regards,
> Brian
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>   


-- 
Bogdan-Andrei Iancu
www.voice-system.ro