[OpenSER-Users] Wrong/Double text appears in Contact header during sequential forking

[liran tal]

Hey everyone,

I'm using sequential forking and on one of the scenarios there appears
to be a problem.

When OpenSER attempts to find the first most relevant destination for the
call the SIP headers are ok. If the first destination that OpenSER attempts
to contact is offline/unreachable it continues to the next one in turn in
which
it produces a bad Contact header which looks like this:

Contact: <sip:101 at 192.168.0.1:5060sip:101 at 192.168.0.1:5060>

As you can see it's writing the sip information twice for some reason.
Has anyone seen this happen before?
Also, where should I be looking at to find the problem?


Thanks,
Lir.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kamailio.org/pipermail/users/attachments/20070724/9552baa7/attachment.htm