Re: [SR-Users] parse_from_header(): bad From header

Problem is solved. The problem was in wrong regeneration of headers in ACK requests (uac restore_mode parameter). This parameter helps to modify From/To headers in all sequential requests and replies in the same way as it has been modified in initial invite. The uac from/to replacement relies

Re: [SR-Users] parse_from_header(): bad From header

Hi Daniel. We are using now kamailio 4.4.6 "the latest release series should have a safety check.." does it mean stable 5.0.4 ? Well it is a reasonable advice I think, we haven't tried this way, yet. I thought about using uac + dialog module together, but this entails a lot of changes in common

Re: [SR-Users] parse_from_header(): bad From header

Hello, it would be useful to know also the version of kamailio that is run there. The latest release series should have a safety check in order to prevent setting an invalid restored From/To URI. On the other hand, if the UA doesn't preserve the From/To, then it doesn't require to be unchanged,

Re: [SR-Users] parse_from_header(): bad From header

Hello, It looks like headers "From" in initial INVITE and received message are different. For example: in INVITE : in received message : When you use header "From" transformation (I see Route with vsf), restore may

Re: [SR-Users] parse_from_header(): bad From header

Hello, It looks like headers "From" in initial INVITE and received message are different. For example: in INVITE : in received message When you use header "From" transformation ( Route with vsf), restore may be correct only for exactly the same header