Re: [OpenSIPStack] upper registration route problem - authentication fails

[OpenSIPStack F. <ope...@op...>]

Don't give up just yet.  I think your server is re-encoding the Via in the response and adding an extra space after SIP/2.0/UDP.  I have applied a patch that would handle this behavior.  Try the latet from CVS and let me know how it goes.

Joegen 

> {quote:title=cam100 wrote:}{quote}
> 
> Hello Joegen,
> 
> 
>  I'm close to give up on that... I have been debugging a lot of things so far - but there is no true result. The only thing I have found is the following:
> 

> The via.GetUri() is called I see a strange behavior when we are parsing the via: headers. I added some debugs in order to find out what it causes: 
> 
> 
> 337287:45:59.687        PWL: [CID=0x0000] show uri in via.GetURI Part 1:
> 337287:45:59.687        PWL: [CID=0x0000] show uri in via.GetURI Part 2, after GetAddress() sip: 85.xx.x.200
> 337287:45:59.687        PWL: [CID=0x0000] show uri in via.GetURI: sip: 85.xx.x.200:5060
>  
> As you can see, we have a space between sip: and the IP Address. What is your opinion ? Can that be the root cause ? I tried to find out where the sip: is added but were unable to. Can you please give me a hint ? Does it make sense to send you a complete SIP trace off list ? Many thanks for your help in advance.
> 
> 
> Regards,
> 
> 
>  Andre  
> 
> 
>  
> 
>