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

[Matthew Ogden]

Perfect, thanks Jon!

One small typo, in case someone else reads your comment when trying to check
the same thing:
ngrep-sip b port 5052 should have been ngrep-sip b port 5062 (the port of
the proxy instance of kamailio).

My understanding of the architecture has increased drastically from this
conversation (and re-reading the manual makes a lot more sense to me now!).

I now have another request from this peer.

They say that my From header should not contain my "auth user" with them,
only my authorization section.
What would be the best way of achieving this? When IP auth is used, SPCE,
sends the correct From, but when authentication is used, SPCE buts the From
User as
From: "CLI" <sip:authuser at peer-realm>

Is there a global setting to change this, or should I be using the
proxy.cfg.customtt.tt2?

Regards

> -----Original Message-----
> From: Jon Bonilla (Manwe) [mailto:jbonilla at sipwise.com]
> Sent: 22 October 2012 11:15 PM
> To: spce-user at lists.sipwise.com
> Cc: Matthew Ogden
> Subject: Re: [Spce-user] adding additional (strange requirement) header
> for a
> peer
>
> El Mon, 22 Oct 2012 22:32:05 +0200
> Matthew Ogden <matthew at tenacit.net> escribió:
>
> > Thanks Jon.
> >
> > Sorry for leaving the reply of the forum, it was by accident.
> >
> > (The header I was trying to add was just  append_hf("TestId:
> > atesthere\r\n"); and I tried it in both sections, i also created an
> > xlog("L_INFO", "Just a logging test");
> >
> > If i grep the logs, it shows, my logging test, but their is no
> > evidence of my Header in ngrep-sip.
> >
>
> Are you capturing the traffic between the proxy and the b2bua? Because
> sems
> will remove your header unless you whitelist it.
>
> Make sure first that the header is present, sent by the proxy with
>
> ngrep-sip b port 5052
>
> and then whitelist your header in sems creating a custom template
>
> /etc/ngcp-config/templates/etc/sems/etc/ngcp.sbcprofile.customtt.tt2