| Author |
|
Jalal
Vetran
Joined: April 24 2006
Location: Iran
Posts: 188
|
| Posted: November 07 2009 at 8:04am | IP Logged
|
|
|
Dear Support,
We had encountered SIP Registeration/Authentication problem while we were testing with Alcatel OmniPCX PBX.
It seems LME does not detect empty string realm. I found when I change realm to a non empty string in Alcatel SIP configurations, LME will successfuly answer WWW-Authenticate with appropriate authentication parameters.
See following logs:
Code:
>>>> Tx:
REGISTER sip:192.168.72.51 SIP/2.0
Via: SIP/2.0/UDP 192.168.72.62:5060;rport;branch=z9hG4bK001500a7
From: <sip:3903@192.168.72.51>;tag=150a69
To: <sip:3903@192.168.72.51>
Call-ID: 53b17bdf-b4f9-464c-aa07-d867a2a92118-00000af8@192.168.72.62
CSeq: 1342967 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:3903@192.168.72.62:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.1 (www.LanScapeCorp.com)
Content-Length: 0
<<<< Rx:
SIP/2.0 401 Unauthorized
WWW-Authenticate: Digest qop="auth",nonce="18d2c8477a72d05951cf1a4176829637",realm=""
To: <sip:3903@192.168.72.51>;tag=0b5a9d045c8d5f2cbc2501ee271e3406
From: <sip:3903@192.168.72.51>;tag=150a69
Call-ID: 53b17bdf-b4f9-464c-aa07-d867a2a92118-00000af8@192.168.72.62
CSeq: 1342967 REGISTER
Via: SIP/2.0/UDP 192.168.72.62:5060;received=192.168.72.62;rport=5060;branch=z9hG4bK001500a7
Content-Length: 0
Global Notification:SipRegisterAuthorizationError
Global Notification:SipRegisterTrying
>>>> Tx:
REGISTER sip:192.168.72.51 SIP/2.0
Via: SIP/2.0/UDP 192.168.72.62:5060;rport;branch=z9hG4bK00152291
From: <sip:3903@192.168.72.51>;tag=14cae9
To: <sip:3903@192.168.72.51>
Call-ID: 53b17bdf-b4f9-464c-aa07-d867a2a92118-00000af8@192.168.72.62
CSeq: 1342968 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:3903@192.168.72.62:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.1 (www.LanScapeCorp.com)
Content-Length: 0
<<<< Rx:
SIP/2.0 401 Unauthorized
WWW-Authenticate: Digest qop="auth",nonce="18d2c8477a72d05951cf1a4176829637",realm=""
To: <sip:3903@192.168.72.51>;tag=7f7556195234fa769aa3ffd7186fc324
From: <sip:3903@192.168.72.51>;tag=14cae9
Call-ID: 53b17bdf-b4f9-464c-aa07-d867a2a92118-00000af8@192.168.72.62
CSeq: 1342968 REGISTER
Via: SIP/2.0/UDP 192.168.72.62:5060;received=192.168.72.62;rport=5060;branch=z9hG4bK00152291
Content-Length: 0
|
|
|
Regards,
Jalal Abedinejad
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: November 10 2009 at 9:43am | IP Logged
|
|
|
Salaam Jalal,
Good to hear from you – and thank you for your post.
We will need to see if this same behavior exits in the current v6.0.0.16 media engine. If it does, it will be easy to locate the issue.
Any chance of letting us remotely access the Alcatel PBX from here? If so, it will speed up the fix/update.
I have added this to our issue list so that we will look into it.
Merci,
Randal
|
| Back to Top |
|
| |
Jalal
Vetran
Joined: April 24 2006
Location: Iran
Posts: 188
|
| Posted: November 11 2009 at 3:47am | IP Logged
|
|
|
Salam Randal,
Thanks for your kindness. I'm glad you answered with Salam.
Unfortunatly we don't have remote access to our Customer site. But I can test your new version on the customer site and report you later.
We currently have set a realm and our problem is solved. So there is no force to fix this bug soon.
Mamnoon :)
Jalal
|
| Back to Top |
|
| |
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Topic: Alcatel SIP Authentication Problem
