Add [last_Header.value] to get only the value part of the last Header

[wdoekes]

Right now [last_From:] and [last_From] are synonymous: they mean the entire header, including the header name.

Quite often, however, you need to put the from-header value in the To header, and vice versa.

This could be simplified if [last_From] meant only the From-header value.

For that change to work, we need a couple of things:

• fix the example scenario's to use colon everywhere
• add the appropriate code to make the distinction
• add an option somewhere to get old-style behaviour (or an option to get new-style?)

Any ideas on that last bit?

I was thinking we could perhaps options to the scenario XML root to accomodate that.

[rkday]

Might be a bit of an obscure distinction, and break existing scripts - could we introduce a new [last_From_value] instead? That gets the same benefit, and is a bit more obvious at first glance.

[vodik]

This is something I've tossed around a bit, I think I'd rather see a dot notation: [last_From.value]. This opens up the notion of "dissection" (e.g. [last_From.user]) if the sip parser is improved (which is something I'm seriously considering because internally we have tonnes of sipp scripts, all using regex to pull particular bits of headers apart and they're not all quite fully RFC compliant).

[wdoekes]

Ooh. I like that extensible [last_From.value] suggestion.

[pbertera]

What about to use the : as a separator instead of . (Eg. [last_From:value])?
The dot can be used into the header names, having an header ending with .value isn't maybe so frequent but something that can happen.