[Spce-user] Peer invite headers

[John Murray]

Andrew,

With this peer I need to register which I do. When I send them calls from my
subscribers I need to put the registering user in the PAI and the subscriber
in the From field. It sounds like this is the opposite to how the SPCE works
by default.
This is a Broadsoft platform.

I've fixed the From: with a custom config file as you suggested. I was
hoping that on the peer config if I selected Auth user it would use the auth
user from the peer itself rather than the subscriber making the call.
Do you think I need to hack this also then in the config file?

Regards

John


-----Original Message-----
From: Andrew Pogrebennyk [mailto:apogrebennyk at sipwise.com] 
Sent: 02 October 2012 10:21
To: John Murray
Cc: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Peer invite headers

Hi John,
Why not use NPN for PAI? It is a subscriber's primary E.164 number or SIP
username when it does not have any E.164 numbers, which should do the same
trick as auth user. What do you think? The auth user is really empty if you
don't authentication your users (you use trusted sources).

On 10/01/2012 08:58 PM, John Murray wrote:
> Andrew,
> 
> Thank you, that seems to have fixed the first problem. I now have the 
> user CLI in the From user field but the peer needs the auth user in 
> the PAI header and I get "No selector set, not setting CLI" in the 
> logs as you guessed correctly I am using trusted sources for the user 
> authentication. My subscribers cannot register or authenticate.
>  
> Any suggestions on a way around this?
> 
> Best regards
> 
> John
> 
> -----Original Message-----
> From: spce-user-bounces at lists.sipwise.com
> [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Andrew 
> Pogrebennyk
> Sent: 01 October 2012 15:26
> To: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Peer invite headers
> 
> Hi John,
> If you authenticate towards your peer the From will be replaced with 
> peer auth user. I think it's written somewhere in the handbook :-)
> 
> It is fairly easily to disable that setting in proxy.cfg.customtt.tt2 
> if your peering does not require it, search for
> if($var(to_pstn) == 1 && isbflagset(FLB_PEERAUTH))
> 
> Regarding PAI header, I have no idea yet why it does not work for you.
> My best guess is that Authentication-User is empty, e.g. you are using 
> trusted sources. In that case you'll see in the log immediately after 
> "Prepare PAI username setting" message saying "No selector set, not 
> setting CLI".
> 
> On 09/28/2012 09:28 PM, John Murray wrote:
>> Hello,
>>
>>  
>>
>> I have SPCE 2.6 with an outbound default peer. The peer config says:
>>
>>  
>>
>> outbound_from_user:                  Received Display-name
>>
>> outbound_from_display:             Received Display-name
>>
>> outbound_pai_user:                      Authentication-User
>>
>>  
>>
>> This is a peer with whom I register and have:
>>
>>  
>>
>> peer_auth_user:
>>
>> peer_auth_pass:
>>
>> peer_auth_realm:
>>
>>  
>>
>> all set.
>>
>>  
>>
>> However INVITES to that peer always have the authentication user in 
>> the From field and no PAI header.
>>
>> I can set the From Display etc and PPI headers but the  From user is 
>> always the authentication user and the PAI header is never there 
>> regardless of how I set them.
>>
>>  
>>
>> Any ideas?
>>
>>  
>>
>> Best regards
>>
>>  
>>
>> John
>>
>>  
>>
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/listinfo/spce-user
>>
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user
>