[Users] Problem with uac_replace and corrupted From

Barry Flanagan barryf-lists at flanagan.ie
Tue Mar 14 16:31:48 CET 2006


Hi,

Using openser 1.1.0-dev8 as a registrar/proxy in from of Asterisk. 
Recently I have been getting errors from Asterisk due to corrupted From: 
headers, which appear to be caused by uac_replace. Here is a section of 
the debug log:


Mar 14 15:12:00 www1 /usr/sbin/openser[7933]: 
DBG:uac::restore_from_reply: removing <From: 
<sip:lenc_domain.com at sip.domain.com>;tag=635c3ce6  >
Mar 14 15:12:00 www1 /usr/sbin/openser[7933]: 
DBG:uac::restore_from_reply: inserting <From: 
<sip:lenc at sip.domain.com>;tag=635c3ce6  >
Mar 14 15:12:00 www1 /usr/sbin/openser[7933]: DEBUG:tm:reply_received: 
org. status uas=200, uac[0]=200 local=0 is_invite=1)
Mar 14 15:12:00 www1 /usr/sbin/openser[7932]: DEBUG:uac:restore_from: 
getting 'vsf' Route param
Mar 14 15:12:00 www1 /usr/sbin/openser[7932]: DEBUG:uac:restore_from: 
Route param is 'aaaaaaaaaaafggqrsqadbekacyvdabuuaw1hz2luzs5pzq--' (len=48)
Mar 14 15:12:00 www1 /usr/sbin/openser[7932]: DEBUG:uac:restore_from: 
decoded uris are: new=[▒�S����
 
                              sN� old=[sip:lenc at sip.domain.com]


As you can see, the auto restore_from of the uri is putting garbled 
characters in there. This has only recently started in the past week. I 
have made no changes to openser in a month. The only thing I did was 
upgrade Asterisk to 1.2.5

Anyone any ideas?
-- 

-Barry Flanagan







More information about the Users mailing list