[OpenSIPS-Users] Mediaproxy 2.1.0: dispatcher - relay problems

[Dan Pascu]

In your own code (see below) I do not see any instruction to set back the 
from_tag. Only the from user and domain.

If you want to change the caller id that way you need to only touch the 
username and domain not the tag in the from field. Removing/changing the 
from tag will make the call fail and no solution will help you make that 
work as the caller phone itself will be unable to recognize answers to 
that session.

On Thursday 11 December 2008, Magnus Burman wrote:
> Glad my groggy brain could help. ;)
>
> I did remove the from_tag, but inserted a new one. Reason for this was
> to get caller id to work. Been trying all kinds of PAI och
> Remote-Party-ID now, but nothing works. They tell me the E.164-number
> must be the user-part of the uri, ie sip:123456798 at domain.
>
> In my route I rewrite the from_tag as late as possible, right before
> the t_relay(). Would mediaproxy be happier if I did this some other
> place, say at the very beginning of the routes?
>
> It also boggles me that it says that "from_tag" not found... because
> it's clearly present. Would it say the same if it didn't understand the
> from_tag? If I remove mediaproxy (which I for my life don't want to do,
> much love your way for this product!), my calls are setup fine,
> caller-id is working and the rtp-data is sent correctly. So with my
> limited knowledge I don't understand why mediaproxy would object...
>
> Again, thanks for a lovely product!
>
> [...]
>
> >>>
> >>> route[1] {
> >>>    ## Forward statefully
> >>>    # Find users caller-id
> >>>    if(avp_db_query("select call_id from subscriber_extras where
> >>> username = '$fU'", "$avp(s:cid)")) {
> >>>        remove_hf("From");
> >>>        append_hf("From: <sip:$avp(s:cid)@<opensips ip>>\r\n",
> >>> "To"); }
> >>>    setflag(1);
> >>>    if (!t_relay()) {
> >>>        sl_reply_error();
> >>>    };
> >>>    exit;
> >>> }


-- 
Dan