[Spce-user] Caller ID Issues with one peer

Sat Sep 17 12:37:18 EDT 2016

Hello, this was provided by my upstream, I dont have a full trace but I can get that soon.
They point out that everything is good in this example:
If we look at your INVITE, this seems to be the case :

From: <sip:289919xxxx at tor.xxx.xxx.ca <mailto:sip%3A2899191273 at tor.trk.tprm.ca>>;tag=68BE9AEB-57D31B9B000A7571-378F8700
To: <sip:1905975xxx8 at tor.xxx.xxx.ca <mailto:sip%3A19059753988 at tor.trk.tprm.ca>>
CSeq: 11 INVITE
Call-ID: 0afe1cc50ed43e023d07fc366c37481a at 172.16.122.132 <mailto:0afe1cc50ed43e023d07fc366c37481a at 172.16.122.132>:5060_b2b-1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
P-Asserted-Identity: <sip:1905963xxx4 at sip.xxxx.ca <mailto:sip%3A19059631054 at sip.optionsdsl.ca>>
Authorization: Digest username="2899191273", realm="tor.xxx.xxxx.ca <http://tor.trk.tprm.ca/>", nonce="959ab751984b", uri="sip:19059753xxx at tor.xxx.xxx.ca <mailto:sip%3A19059753988 at tor.trk.tprm.ca>", qop=auth, cnonce="2b87d3c9", nc=00000001, response="a954dab7e440b1821104776900896272", algorithm=MD5

But, the CLI you sent in the FROM header . Right now, you are sending 289919xxxx. It should look like

From: <sip:1905963xxx4 at sip.xxxxx.ca <mailto:sip%3A19059631054 at sip.optionsdsl.ca>>

This also from my upstream:

The CLI is taken in the FROM header.

Password authentication should be sent in the "Authorization" header of the re-invite.

The re-invite is all correct from you it is just the From-header that is wrong.

They don't use PAI for anything, it is ignored. So change the from header and all should be fine.

Again this only happens on a peer I authenticate with username and password.

> On Sep 17, 2016, at 5:28 AM, Raúl Alexis Betancor Santana <rabs at dimension-virtual.com> wrote:
> 
> Could you please send a trace of a call going out and what it's supposed your carrier wants ? ... because it's too weird it doesn't work as espected.
> 
> 
> De: "Dave Massey" <dave at optionsdsl.ca>
> Para: "Raúl Alexis Betancor Santana" <rabs at dimension-virtual.com>
> Enviados: Sábado, 17 de Septiembre 2016 1:33:34
> Asunto: Re: [Spce-user] Caller ID Issues with one peer
> Ok. Anyone knowledgeable on how to modify the templates? I only have one auth peer, so changing it globally is ok
> 
> Thanks!
> 
> On Sep 16, 2016, at 4:17 PM, Raúl Alexis Betancor Santana <rabs at dimension-virtual.com <mailto:rabs at dimension-virtual.com>> wrote:
> 
> Thats because peer_auth is done by sems, you should modify the sems templates to outbound auth peers ... but will be globaly changed to all outbound peers that uses auth
> 
> 
> De: "Dave Massey" <dave at optionsdsl.ca <mailto:dave at optionsdsl.ca>>
> Para: "Raúl Alexis Betancor Santana" <rabs at dimension-virtual.com <mailto:rabs at dimension-virtual.com>>
> Enviados: Viernes, 16 de Septiembre 2016 20:10:49
> Asunto: Re: [Spce-user] Caller ID Issues with one peer
> Yes that option is there, but it doesnt resolve the issue Im having, it doesnt actually change the From-Header if Im using peer authentication.
> 
> Thanks
> 
> On Sep 16, 2016, at 1:07 PM, Raúl Alexis Betancor Santana <rabs at dimension-virtual.com <mailto:rabs at dimension-virtual.com>> wrote:
> 
> I don't remember if the 3.1 have the options I told you on the previous email ... go and check if you have this options on gateway preferences.
> 
> 
> 
> 
> De: "Dave Massey" <dave at optionsdsl.ca <mailto:dave at optionsdsl.ca>>
> Para: "Raúl Alexis Betancor Santana" <rabs at dimension-virtual.com <mailto:rabs at dimension-virtual.com>>
> Enviados: Viernes, 16 de Septiembre 2016 16:51:12
> Asunto: Re: [Spce-user] Caller ID Issues with one peer
> Updating to 3.8 I can control this from right within the GUI even on a peer I authenticate against?  
> My peer tells me I'm doing auth in the reINVITE and that's working ok. 
> 
> On Sep 16, 2016, at 10:05 AM, Raúl Alexis Betancor Santana <rabs at dimension-virtual.com <mailto:rabs at dimension-virtual.com>> wrote:
> 
> 
> Quite old men! ...
> 
> On the 3.8.X you could select how you want to send the callerID on each peer basics.
> 
> If I undestand your ok, you are willing to auth your outgoing calls to your upstream provider, but you need the auth-user to be on the From, is that ok?
> 
> What is exactly the situation, how you upstream provider auth you?
> 
> De: "Dave Massey" <dave at optionsdsl.ca <mailto:dave at optionsdsl.ca>>
> Para: "Skyler" <skchopperguy at gmail.com <mailto:skchopperguy at gmail.com>>
> CC: spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com>
> Enviados: Viernes, 16 de Septiembre 2016 15:05:37
> Asunto: Re: [Spce-user] Caller ID Issues with one peer
> Sorry. 3.1
> 
> On Sep 16, 2016, at 4:11 AM, Skyler <skchopperguy at gmail.com <mailto:skchopperguy at gmail.com>> wrote:
> 
> what version are you running?
> 
> --Skyler
> 
> 
> On Sep 14, 2016 5:27 PM, "Dave Massey" <dave at optionsdsl.ca <mailto:dave at optionsdsl.ca>> wrote:
> Bump for any help if it can be done? My upstream needs me to figure this out in the next couple days.
> 
> > On Sep 12, 2016, at 4:31 PM, Dave Massey <dave at optionsdsl.ca <mailto:dave at optionsdsl.ca>> wrote:
> >
> > 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 <mailto: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>
> >>> <mailto: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 <tel:%2B4312345>"
> >>>> <sip:+4312345 at your-domain.com <mailto:sip%3A%2B4312345 at your-domain.com> <mailto:4312345 at your-domain.com <mailto:4312345 at your-domain.com>>>. If
> >>>> you DO authenticate, then the From header is "+4312345 <tel:%2B4312345>"
> >>>> <sip:your_peer_auth_user at your_ <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:sip%3A%2B4312345 at your-domain.com>
> >>>> <mailto: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>
> >>>> <mailto: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>
> >>>>       <mailto: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:sip%3A19057722572 at sip.optionsdsl.ca>
> >>>>   <mailto:19057722572 at sip.optionsdsl.ca <mailto:19057722572 at sip.optionsdsl.ca>>>' -
> >>>>   R=sip:19059753988 at 209.15.226.21 <mailto:sip%3A19059753988 at 209.15.226.21> <mailto:19059753988 at 209.15.226.21 <mailto:19059753988 at 209.15.226.21>>
> >>>>   ID=f2316165-fddb0614-d0aaadf7 at 10.40.36.100 <mailto:f2316165-fddb0614-d0aaadf7 at 10.40.36.100>
> >>>>   <mailto:ID <mailto:ID>=f2316165-fddb0614-d0aaadf7 at 10.40.36.100 <mailto: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:sip%3A2899191273 at tor.trk.tprm.ca>
> >>>>   <mailto:2899191273 at tor.trk.tprm.ca <mailto:2899191273 at tor.trk.tprm.ca>>>' -
> >>>>   R=sip:19059753988 at 206.80.250.100 <mailto:sip%3A19059753988 at 206.80.250.100>
> >>>>   <mailto:19059753988 at 206.80.250.100 <mailto:19059753988 at 206.80.250.100>>
> >>>>   ID=6596d56-a2187651-9a413210 at 10.40.36.100 <mailto:6596d56-a2187651-9a413210 at 10.40.36.100>
> >>>>   <mailto:ID <mailto:ID>=6596d56-a2187651-9a413210 at 10.40.36.100 <mailto: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 <tel:2899191273> on the
> >>>>   callee’s phone
> >>>>
> >>>>   Thanks
> >>>>   _______________________________________________
> >>>>   Spce-user mailing list
> >>>>   Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com> <mailto:Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>>
> >>>>   https://lists.sipwise.com/listinfo/spce-user <https://lists.sipwise.com/listinfo/spce-user>
> >
> > _______________________________________________
> > Spce-user mailing list
> > Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> > https://lists.sipwise.com/listinfo/spce-user <https://lists.sipwise.com/listinfo/spce-user>
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> https://lists.sipwise.com/listinfo/spce-user <https://lists.sipwise.com/listinfo/spce-user>
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> https://lists.sipwise.com/listinfo/spce-user <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/20160917/eaa41965/attachment-0001.html>