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

[Matthew Ogden]

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.

I'm guessing I am overlooking something, but not sure what.


> -----Original Message-----
> From: Jon Bonilla (Manwe) [mailto:jbonilla at sipwise.com]
> Sent: 22 October 2012 06:27 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 09:25:16 +0200
> Matthew Ogden <matthew at tenacit.net> escribió:
>
> > Thanks Jon
> >
> > I'm not very familiar with how this works, I have a development
> > background, but am still growing my understanding of how everything
> integrates in SPCE.
> >
> > Are you saying that I should look at the BRANCH_ROUTE_CLI_RTP just if
> > I want some logic to be based on the IP of the peer?
> >
> > Is the original place I was looking at correct for adding of my custom
> > P-A-I? ( i), or are you saying I must only do this in
> > BRANCH_ROUTE_CLI_RTP.
> >
> >
>
> Please keep the mailing list in CC
>
> Sorry I didn't answer before. I'm in Kassel the whole week and not in the
> office.
>
> ROUTE_SET_CLI_CALLER is called from BRANCH_ROUTE_CLI_RTP anyways. You ca
> nset
> your custom header after ROUTE_PSTN (where the gw ip address is loaded)
> and
> after you set the $du for the PSTN gw. And yes, the call to that function
> takes place after that.
>
> I'd recommend you to add xlog lines and investigate the logs with ngrep
> captures to debug your header manipulations.
>
>
> cheers,
>
> Jon