[Spce-user] Caller ID Issues with one peer

[Dave Massey]

My upstream takes the password authentication from the reINVITE and that's working fine. They ignore the PAI and take the CLI in the From-header.  

Is it difficult to change this in SPCE for this peer?

> On Sep 12, 2016, at 11:39 AM, Daniel Grotti <dgrotti at sipwise.com> wrote:
> 
> Hi,
> well, how your peer would authenticate you then ? Using the PAI header ?
> Usually the authentication is based on the From header, are you sure that you provider will be able to authenticate your user with "username" in PAI and not in From ?
> 
> 
> Daniel
> 
> 
>> On 09/12/2016 04:57 PM, Dave Massey wrote:
>> Is there any way to change this ? In the code?
>> 
>> From my upstream:
>> 
>> Looks like you will have to change some code on your SPCE. it sends the
>> CLI in P-Asserted-Identity and upstream pulls it in From-header.
>> 
>> I need the CLI in From-header on a peer I authenticate against.
>> 
>> Thanks.
>> 
>> 
>> 
>> 
>> On Sep 9, 2016, at 1:52 PM, Daniel Grotti <dgrotti at sipwise.com
>> <mailto:dgrotti at sipwise.com>> wrote:
>> 
>>> Hi Dave,
>>> From handbook:
>>> "If you do NOT authenticate against a peer host, then the caller CLI
>>> is put into the From and P-Asserted-Identity headers, e.g. "+4312345"
>>> <sip:+4312345 at your-domain.com <mailto:4312345 at your-domain.com>>. If
>>> you DO authenticate, then the From header is "+4312345"
>>> <sip:your_peer_auth_user at your_peer_auth_realm>(the CLI is in the
>>> Display field, the peer_auth_user in the From username and the
>>> peer_auth_realm in the From domain), and the P-Asserted-Identityheader
>>> is as usual like <sip:+4312345 at your-domain.com
>>> <mailto:4312345 at your-domain.com>>. So for presenting the correct CLI
>>> in/CLIP//no screening/ scenarios, your peering provider needs to
>>> extract the correct user either from theFrom Display-Name or from
>>> the P-Asserted-Identity URI-User."
>>> 
>>> Cheers,
>>> Daniel
>>> 
>>> 
>>> On Sep 9, 2016 6:16 PM, Dave Massey <dave at optionsdsl.ca
>>> <mailto:dave at optionsdsl.ca>> wrote:
>>> 
>>>    Bumping for any ideas?
>>>    Ive messed with the peer number manipulation section to no avail.
>>> 
>>>    Thanks
>>> 
>>>        On Jul 21, 2016, at 2:11 PM, Dave Massey <dave at optionsdsl.ca
>>>        <mailto:dave at optionsdsl.ca>> wrote:
>>> 
>>>    I have 2 peers configured, one uses IP authentication (no
>>>    username/password/realm entered) and one that uses
>>>    username/password/realm for outgoing calls.
>>>    The peer that uses IP authentication works fine for displaying
>>>    correctly the caller ID on the called partys phone, but the one
>>>    that uses authentication always puts the username/realm as the “From”
>>> 
>>> 
>>> 
>>>    This one works OK, the From contains the number Im calling:
>>>    proxy <script>: Setting From to
>>>    '<sip:19057722572 at sip.optionsdsl.ca
>>>    <mailto:19057722572 at sip.optionsdsl.ca>>' -
>>>    R=sip:19059753988 at 209.15.226.21 <mailto:19059753988 at 209.15.226.21>
>>>    ID=f2316165-fddb0614-d0aaadf7 at 10.40.36.100
>>>    <mailto:ID=f2316165-fddb0614-d0aaadf7 at 10.40.36.100>
>>> 
>>> 
>>> 
>>>    When I call the same number out this new peer it changes it to below:
>>>    proxy[4378]: NOTICE: <script>: Setting From to
>>>    '<sip:2899191273 at tor.trk.tprm.ca
>>>    <mailto:2899191273 at tor.trk.tprm.ca>>' -
>>>    R=sip:19059753988 at 206.80.250.100
>>>    <mailto:19059753988 at 206.80.250.100>
>>>    ID=6596d56-a2187651-9a413210 at 10.40.36.100
>>>    <mailto:ID=6596d56-a2187651-9a413210 at 10.40.36.100>
>>> 
>>>    Where do I change it so it does the same thing as the first peer?
>>>    Calls out work fine but always display the 2899191273 on the
>>>    callee’s phone
>>> 
>>>    Thanks
>>>    _______________________________________________
>>>    Spce-user mailing list
>>>    Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>    https://lists.sipwise.com/listinfo/spce-user
>>> 
>>>