Username mismatch have <1531> digest has <>

Asterisk Asterisk Support
1

Hi,

I’m running Asterisk 1.8.5.0. I have 2 Polycom phones setup exactly the same just different extension numbers etc.

I am also using Realtime Sip to add and remove the Polycom Phones. I have one phone which registers ok and all is working fine, the second phone when it tries to register I get a the above message, I have run a Sip Debug and can see the following

<— SIP read from UDP:...:5060 —>
REGISTER sip:...:5060 SIP/2.0
Via: SIP/2.0/UDP ...;branch=z9hG4bKa1cd9351EB044DFE
From: “Services” sip:1531@*.*.*.*;tag=44168D6B-D869510
To: sip:1531@*.*.*.*
CSeq: 2 REGISTER
Call-ID: a66b9344-b676375-2e59f152@...
Contact: sip:1531@*.*.*.*;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"
User-Agent: PolycomSoundPointIP-SPIP_650-UA/3.0.4.0061
Authorization: Digest username="", realm=“asterisk”, nonce=“041fc0db”, uri=“sip:...:5060”, response=“0aaf81fcedfc3cf24556246ff4027b5d”, algorithm=MD5
Max-Forwards: 70
Expires: 3600
Content-Length: 0

I can see that the part I marked as bold being the problem, though I don’t know what to do to fix this issue, as I said earlier I have another phone with the same settings and it’s ok.

Thanks in advance

2

The phone configurations aren’t the same. One of them has an empty authorisation user name (it might be something like a space that prevents a default being taken).

3

Thanks for the reply david55.

I have checked the Polycom phone settings in the web interface and there is definitely no spaces or missing entries. I have

Address 1531
Auth User ID 1531
Auth Password XXXX

Do you have any further suggestions? Thanks again

4

Bug in the phone, as it is definitely not sending auth user-id.

5

Ok, Thanks,

I’ll try updating the SIP version on the phone and see how that works

6

david55, thanks

Updated Polycom Sip version from 3.0.4.0061 to 3.2.5.0508 has done the trick.

Strange thing is the other phone has the same version as the one I had before. I suppose I can expect problems with that later.