[Spce-user] P-Asserted-Identity

[Barry Flanagan]

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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20170309/600dc581/attachment-0001.html>