Arunkarthicknallasami / siphon

Automatically exported from code.google.com/p/siphon
0 stars 0 forks source link

Siphon Settings: Credentials - Not possible to set Username unequal Authorization name #20

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. No Steps needed

What is the expected output? What do you see instead?
This is more a change request for beeing able to configure username and 
authoization name different.
Example:
Username is user part of SIP URI: oetzi5678
Auth.name is used in SIP header Authorization: oetzi8765   

What version of the product are you using? On what operating system?
iphone 1.1.4

Please provide any additional information below.
Example REGISTER with Username different Authorization name:

       REGISTER sip:registrar.sip.com SIP/2.0
       Via: SIP/2.0/UDP 192.0.2.4:5060;branch=z9hG4bKnashds7
       Max-Forwards: 70
       To: Bob <sip:oetzi5678@sip.com>
       From: Bob <sip:oetz5678@sip.com>;tag=456248
       Call-ID: 843817637684230@998sdasdh09
       CSeq: 1826 REGISTER
       Contact: <sip:oetzi5678@192.0.2.4>
       Authorization: Digest 
username="oetzi8765",realm="sip.com",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c
093",uri="sip:oetz5678@sip.com",qop=auth,nc=00000001,cnonce="0a4f113b",resp
onse="6629fae49393a05397450978507c4ef1",opaque="5ccc069c403ebaf9f0171e9517f
40e41"
       Expires: 3600
       Content-Length: 0

Thanks in advance
oetzi5678

Original issue reported on code.google.com by oetzi5...@gmail.com on 4 Jul 2008 at 9:19

GoogleCodeExporter commented 8 years ago
In fact, you want to change Contact information ?
In this case, it will be easy to do. But I wanted something easy to use.

Could you confirm ?

Original comment by samuelv0...@gmail.com on 6 Jul 2008 at 8:37

GoogleCodeExporter commented 8 years ago
Hi Samuel,
sorry for the delay. I understand your point of having something simple with 
less 
complexity. The point is that many providers do have for security reason 
username 
different than authorization name. I am looking for the possibility to have the 
user 
part of the SIP URI different than the "username" (I call it Authorization 
name) 
used to authenticate SIP Requests as REGISTER, INVITE, BYE, SUBSCRIBE etc.
To be more clear a better example below for a REGISTER sent after receiving a 
401 
Unauthorized. 

       REGISTER sip:registrar.sip.com SIP/2.0
       Via: SIP/2.0/UDP 192.0.2.4:5060;branch=z9hG4bKnashds7
       Max-Forwards: 70
       To: Oetzi <sip:oetzi@sip.com>
       From: Oetzi <sip:oetzi@sip.com>;tag=456248
       Call-ID: 843817637684230@998sdasdh09
       CSeq: 1826 REGISTER
       Contact: <sip:oetzi@192.0.2.4>
       Authorization: Digest 
username="+445567897646",realm="sip.com",nonce="dcd98b7102dd2f0e8b11d0f600bfb0c
093",uri="sip:oetzi@sip.com",qop=auth,nc=00000001,cnonce="0a4f113b",resp
onse="6629fae49393a05397450978507c4ef1",opaque="5ccc069c403ebaf9f0171e9517f
40e41"
       Expires: 3600
       Content-Length: 0

The Setting GUI could give the possibility to enter:
Username: Oetzi                 # even better SIP URI Oetzi@sip.com
Auth.name: +445567897646        # This field could be some kind of hidden till 
a 
checkbox is entered with "Username different Auth.name" else only Username is 
visible
Password: *******               # no changes here
Server: sip.com                 # many providers do have an outbound proxy 
server 
where the SIP domain is not equal to the IP domain. If the PJSIP stack doesn't 
support RFC 3263 (DNS SRV and NAPTR) it would be great to have the possibilty 
to 
enter the IP domain or directly the IP address e.g. sip.com is the SIP domain 
and 
will be addressed only in SIP messages wherby the messages itself are sent to 
sip_obp.com (50.50.1.1) the address of the SBC. If you could setup like in the 
example you wouldn't need an extra field for it. People would enter:
SIP URI: Oetzi@sip.com      [checkbox]
[Username: +445567897646]      #optional
Password: *******
[SIP Server: sip_obp.com]      #optional if different to sip.com

After so much text it looks like 2 fields would be enough for ordinary users 
and 2 
extra fields would make your SIP client really mighty because it could run at 
any 
provider. I was thinking in joining the project but don't know if I really 
could 
help or not. Let me know if this is realistic to make it happen or not.
Thanks in advance.
Oetzi5678

Original comment by oetzi5...@gmail.com on 8 Jul 2008 at 9:19

GoogleCodeExporter commented 8 years ago
Use different values for id and username parameters.

Original comment by samuelv0...@gmail.com on 11 Nov 2008 at 4:41

GoogleCodeExporter commented 8 years ago

Original comment by samuelv0...@gmail.com on 4 Dec 2008 at 2:19

GoogleCodeExporter commented 8 years ago
Issue 87 has been merged into this issue.

Original comment by samuelv0...@gmail.com on 3 Jan 2009 at 10:37

GoogleCodeExporter commented 8 years ago
Issue 91 has been merged into this issue.

Original comment by samuelv0...@gmail.com on 3 Jan 2009 at 10:37

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Just to echo the point that oetzi5678 brought forward:

Many ITSP/SIP providers for business accounts do require both AUTH USER and 
USER data, which are different 
for security reasons. For example, here is the documentation from Junction 
Networks/onSIP: 
http://www.junctionnetworks.com/knowledgebase/onsip/devices/phone-configuration/
generic-sip-phone-
configuration

The only additional issue that should be retained from Issue 91 is that in the 
USER (and eventually AUTH 
USER) field, you should allow the "@" symbol.

Original comment by avery.gl...@gmail.com on 3 Jan 2009 at 11:18

GoogleCodeExporter commented 8 years ago
I copy example from the above link :
# Address of Record : hiro@example.onsip.com
# SIP Password      : VPG3hockrifv
# Auth Username     : example_hiro
# Username          : hiro
# Proxy/Domain      : example.onsip.com

For the moment, Siphon uses :
# SIP Password      : VPG3hockrifv
# Username          : hiro
# Proxy/Domain      : example.onsip.com
And it builds address of record by concatenation of username and Proxy/Domain.
(Username@example.onsip.com).
In the next version I will add Authentication Username in advanced settings.

I think, it will be correct, won't it ?

Original comment by samuelv0...@gmail.com on 4 Jan 2009 at 12:04

GoogleCodeExporter commented 8 years ago
Yes - the Address of Record is essentially username@domain. If you add in the 
Auth Username in advanced 
settings, that should be pretty much it!

Original comment by avery.gl...@gmail.com on 4 Jan 2009 at 12:09