[Spce-user] adding additional (strange requirement) header for a peer

[Matthew Ogden]

Indeed, big big company (our countries biggest retail ISP ), trying to
compete against other players in the market, but still lacking experience
from what I can gather

Maybe Sipwise must approach them!

> -----Original Message-----
> From: Jon Bonilla (Manwe) [mailto:jbonilla at sipwise.com]
> Sent: 23 October 2012 12:35 AM
> To: spce-user at lists.sipwise.com
> Cc: Matthew Ogden
> Subject: Re: [Spce-user] adding additional (strange requirement) header
> for a
> peer
>
> El Tue, 23 Oct 2012 00:26:08 +0200
> Matthew Ogden <matthew at tenacit.net> escribió:
>
> > I think you can ignore that last question, and anyone else can refer to:
> >
> > http://lists.sipwise.com/pipermail/spce-user/2011-August/000557.html
> > http://lists.sipwise.com/pipermail/spce-user/2012-April/001235.html
> >
> >
> In case you still need to disable setting the auth credentials in the From
> header I think you could remove this "if" and always hit the "else" part
> of
> it:
>
> if($var(to_pstn) == 1 && isbflagset(FLB_PEERAUTH))
>   {
>   $var(caller_uri) = "sip:" + $avp(s:peer_peer_caller_auth_user) + "@" +
>   $avp(s:peer_peer_caller_auth_realm);
>
>   }
> else
>   {
>
>
> But as you said, the default behaviour should be to send the auth username
> in
> the From and the cli in the PAI header. Accepting that depends on your
> provider. Looks quite "unique"
>
>
> cheers,
>
> Jon