P-Asserted Identity

[Todd Hodgen]

In 16.08 there were changes in the Proxy to allow for enabling P-Asserted Identity, from a Jira that was out there.   SIPX-404.  

 

I have a SIP provider I’ve used for years without issue that is now complaining that I’m not providing P-asserted Identity.   I’ve found where it is enabled now in Proxy, but doesn’t seem to make a difference.  This may be a SIP provider issue, but trying to figure that out now.  Having the same issue now at two different sipXcom sites.

 

Has anyone had any issues with P-Asserted Identity with SIP trunks have any sage suggestions they can share to work through this issue?  Currently, they are both running 17.08.   Fix was put in in 16.08

 

Todd R. Hodgen

President & Founder

SIP Telecom

206-432-4344 – Direct

t.ho...@SIPTelecom.Systems

 

 

“Love Rain, Snow, Sleet, Hail, Lightning, Tornadoes?  Then you will love the cloud!”

 

[George Niculae]

Hi Todd,

I don't think that was really fixed (but only UI option added) SIPX-404 should have been paired with http://jira.sipxcom.org/browse/SIPX-403 for a complete fix

Cheers,

George

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CY1PR07MB2425832262FF4CF8909FE83AFD4C0%40CY1PR07MB2425.namprd07.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

[Todd Hodgen]

Any idea then what may have changed to affect behavior in sipxcom?  Problem may be elsewhere.  Just trying to understand it.

sent by my two left twiddling thumbs...

---

From: George Niculae <geo...@ezuce.com>
Sent: Wednesday, October 18, 2017 5:35:56 AM
To: Todd Hodgen
Cc: sipxcom-users
Subject: Re: [sipxcom-users] P-Asserted Identity

 

[cmasc...@gmail.com]

Frankly I don't know what sipXproxy "Pass P-Asserted-Identity" does, but for SIP trunking I think you need to check the SBC settings rather than the proxy settings. If you are using sipXbridge see this WIKI page:

http://wiki.sipxcom.org/display/sipXcom/SIP+Trunking

If the SBC settings look correct I'd do a packet capture of the SBC's INVITE to verify the presence and content of P-Asserted-Identity.

If this was working and just stopped working one day, and you hadn't changed anything, then something must have changed at your ITSP.

[Todd Hodgen]

It’s a bit different than that.  Feature works on different systems, running older versions.   Just installing two new systems, using the same ITSP, and the feature is not work with current release.   The issue is when you put a different Caller-ID for an extension, the ITSP complains about P-Asserted-Identity issues.  Works fine with other carriers.  I do suspect it is the carrier, and will be doing captures today.  However, looking at notes for software updates from where it worked in the past up to the current release, I found the update notes about a change in P-asserted-Identity, so needed to do my due diligence to ensure I wasn’t chasing a ghost.

 

I’ll also try with a different ITSP to see if it works to help prove the issue to this particular carrier.

--

You received this message because you are subscribed to the Google Groups "sipxcom-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.

To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/6df730ad-34df-44ac-a702-c2b64bea1e1f%40googlegroups.com.

[cmasc...@gmail.com]

First, if I understood George correctly, it's not possible to pass the phone's P-Asserted-Identity because the sipXproxy dialog option isn't "wired up" to anything.

Second, if you did set the SIP username in P-Asserted-Identity to anything other than the SIP auth. username on the ITSP account, the ITSP should indeed complain about that because it's not an identity that the ITSP has authenticated.

[cmasc...@gmail.com]

I'd like to correct an error in my previous post.
Disregard the paragraph starting "Second, ...".
I just looked at P-Asserted-Identity in a 17.04 sipXbridge INVITE: the SIP username is the gateway's Default Caller ID. (I'm not using per-user caller ID.) It doesn't need to be the SIP auth. username.