On 10/2/15 8:42 AM, Roger Wiklund wrote:
Hi list!
We are testing out SIPREC in our Acme SBCs.
The goal is to be "PBX neutral" for a lack of a better word.
We are using Verba as SRS.
Basic incoming and outgoing calls work fine. SRC sends SIPREC INVITE
to SRS with metadata containing A och B parties.
Now, 100% of our customers that want to use call recording of course
sometimes transfers the call within the PBX or out to the PSTN.
The PBX then sends a re-INVITE or UPDATE to the Acme SBC with a
P-Asserted-Identity containing the new participant.
When we use port mirror (SPAN) with Verba, they have support for PAI
participant change and will start/stop recording based on it.
This is not the case with SIPREC. There is no P-Asserted-Identity sent
in the SIPREC XML.
I've looked at the siprec draft 18 and it mentions P-Asserted-Identity
as an additional AOR.
Has this specific transfer case without REFER been discussed?
I don't recall if this sort of transfer was explicitly discussed. But
the spec is intentionally vague on what should be used as the source of
participant info. It doesn't say it should come from From/To.
The SRC is expected to choose appropriate sources from the signaling in
the CS. And allowing multiple AoR/Name pairs means that the SRC doesn't
need to pick just one.
Is there any leverage that I can use towards the vendor to have them
implement this? (I.E follow the standard).
There isn't anything that says "you are non-conforming if you don't
include P-A-ID".
This is more a matter of whether you have a useful implementation or
just a token (check the box) implementation.
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
