[OpenSIPS-Users] Strange username registration

[Douglas Lane]

Hi Brett,

I haven't made any changes, as the changes I made last night with 
Vallimamod, I had to quickly undo as I lost a few asterisk registrations ;-)

IP 1.2.3.4 is the client
IP 5.6.7.8 is the server

Here is a registration from Asterisk server - it is successful:
U 1.2.3.4:5060 -> 5.6.7.8:5060
REGISTER sip:domain.com SIP/2.0.
Via: SIP/2.0/UDP 1.2.3.4:5060;branch=z9hG4bK0f391872;rport.
Max-Forwards: 70.
From: <sip:finlogicvpbx at domain.com>;tag=as45515d65.
To: <sip:finlogicvpbx at domain.com>.
Call-ID: 2016b5f0057cbb960c5f688437c0915a at 1.2.3.4.
CSeq: 417 REGISTER.
User-Agent: Asterisk PBX 1.6.0.10-FONCORE-r40.
Authorization: Digest username="finlogicvpbx at domain.com", 
realm="domain.com", algorithm=MD5, uri="sip:domain.com", 
nonce="4bbebbfa0000574e9410cd08b00ba31be31b378189e1d9e8", 
response="f4bb7a3479e82c35aa5122c652620571".
Expires: 120.
Contact: <sip:s at 1.2.3.4>.
Event: registration.
Content-Length: 0.

Upon the save("location") function, the above registration is saved into 
the location database as user_column=finlogicvpbx, domain=domain.com.
This is CORRECT and I'm happy with it.


And here is the every great Xlite (Siemens A580 is pretty much identical)
T 1.2.3.4:58889 -> 5.6.7.8:5060 [AP]
REGISTER sip:domain.com SIP/2.0.
Via: SIP/2.0/TCP 
192.168.0.236:10990;branch=z9hG4bK-d8754z-375adf06ebab9063-1---d8754z-;rport. 

Max-Forwards: 70.
Contact: 
<sip:doug%40domain.com at 1.2.3.4;rinstance=0051b76a880b6325;transport=TCP>.
To: <sip:doug%40domain.com at domain.com>.
From: <sip:doug%40domain.com at domain.com>;tag=7adae37b.
Call-ID: ZDlmN2JmMmY4ZjdmYTU2MmI5YzAyYjZmMTE4ODBjY2Q..
CSeq: 2 REGISTER.
Expires: 3600.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, 
SUBSCRIBE, INFO.
User-Agent: X-Lite Beta release 4.0 v3 stamp 55153.
Authorization: Digest 
username="doug at domain.com",realm="domain.com",nonce="4bbc186000007a99f8b3ca45e77563c7b19f6ea461817c3e",uri="sip:domain.com",response="96bf9f599ddf3057c5bc48faf9a1d923",algorithm=MD5. 

Content-Length: 0.

However, the  same save("location") function, the above registration is 
saved into the location database as user_column=doug at domain.com, 
domain=domain.com.
This is INCORRECT and causes problems for billing (without modifying my 
billing_party id accordingly).

It also looks horrible when I do a network status in CDR tool, and there 
is this one account that is in the domain "domain [dot] com [at] domain 
[dot] com".

Perhaps I need to strip out the From / To headers of any bad data like 
%40? Or maybe there is another way to force location to use the Auth 
Username and Auth Realm instead of the From Header?

Thanks
Doug


On 2010/04/09 7:14 AM, Brett Nemeroff wrote:
> I didn't see the new problem posted. Maybe I missed it? :)
>
>    
>> Now when I try the same with an Xlite or a Siemens A580IP (those are the
>> only 2 devices I have tried so far), the only difference between the
>> asterisk registration and the xlite is the From header and To header in
>> the asterisk registration contains username [at] domain [dot] com,
>>      
>
> You mentioned that with the change you made, user is in the user field
> and domain is in the domain field.. but didn't mention how that
> differs from what's in the location table with xlite or the siemens.
> Maybe a sample of the table data posted would be helpful?
>
> Thanks,
> Brett
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>