[Spce-user] P-Asserted-Identity

[Barry Flanagan]

On 9 March 2017 at 15:36, <jchism2 at gmail.com> wrote:

> P asserted identity is set at the peering or subscriber level on
> inbound_upn and inbound_npn.  You have the option to choose Remote-Party-ID
> instead of P-Asserted-Identity.
>
>
Yes, but Christopher's issue is his downstream wants the RPID header - so
on outbound. There is no option for that.

-Barry



> Sent from my iPhone
>
> On Mar 9, 2017, at 9:28 AM, Christopher Saroli <csaroli at isysp.com> wrote:
>
> *“I don't think  Remote-Party-ID is supported in spce.”*
>
>
>
> Can anyone confirm this?
>
>
>
>
>
> Thanks for the insight Barry
>
>
>
>
>
> ---------------------------------
>
> *Christopher Saroli*
>
> csaroli at isysp.com
>
> <image001.jpg><image002.png>
>
>    (586)226-7800 * www.isysp.com
>
>
>
> *From:* Barry Flanagan [mailto:barry at flanagan.ie <barry at flanagan.ie>]
> *Sent:* Thursday, March 09, 2017 10:25 AM
> *To:* Christopher Saroli <csaroli at isysp.com>
> *Cc:* spce-user at lists.sipwise.com
> *Subject:* Re: [Spce-user] P-Asserted-Identity
>
>
>
> On 9 March 2017 at 15:09, Christopher Saroli <csaroli at isysp.com> wrote:
>
> I started having issues recently and called my carrier and they said this
>
>
>
> *I believe the issue is the inclusion of "P-Asserted-Identity" in your
> invite packet. It is not a supported format and causes known issues. Please
> utilize "Remote-Party-ID"*
>
>
>
> Hmm. As far as I know, while "P-Asserted-Identity" is a standard (defined
> in RFC 3325),  "Remote-Party-ID" is not - although it is implemented
> quite widely, it was never accepted.
>
>
>
>
>
>
>
> Can anyone point me in the right direction to change this setting? Any
> help would be greatly appreciated.
>
>
>
> I don't think  Remote-Party-ID is supported in spce.
>
>
>
> -Barry Flanagan
>
>
>
> ---------------------------------
>
> *Christopher Saroli*
>
> csaroli at isysp.com
>
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170309/01a5ec04/attachment-0001.html>