29 May
2005
29 May
'05
4:19 a.m.
Never had any problem with digest auth, but yes, we had some problems with
the IP address.
However, here is the top of a current (after firmware upgrade) INVITE from a
Polycom:
U 2005/05/27 10:50:42.733599 nat:2631 -> ser:5060
INVITE sip:number@ourdomain.com;user=phone SIP/2.0.
Via: SIP/2.0/UDP 10.2.2.54;branch=z9hG4bK7323c8ac29B7807.
From: "Username" <sip:userid@ourdomain.com>;tag=9DFAF7D6-DB7B7E5B.
To: <sip:number@ourdomain.com;user=phone>.
CSeq: 2 INVITE.
Call-ID: b07f3daa-4ce9e980-6bf54d45(a)10.2.2.54.
Contact: <sip:userid@10.2.2.54>.
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY,
PRACK, UPDATE, REFER.
User-Agent: PolycomSoundPointIP-SPIP_300-UA/1.4.1.
As you can see, this is firmware 1.4.1.
Here's a REGISTER:
U 2005/05/27 10:56:36.553574 nat:2631 -> ser:5060
REGISTER sip:ourdomain.com SIP/2.0.
Via: SIP/2.0/UDP 10.2.2.54;branch=z9hG4bKf6e50949F4082504.
From: "Username" <sip:userid@ourdomain.com>;tag=D548EE73-DCDBC98.
To: <sip:userid@ourdomain.com>.
CSeq: 845 REGISTER.
Call-ID: 12d50ac7-c547e35d-a024f6c2(a)10.2.2.54.
Contact: <sip:userid@10.2.2.54>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS,
INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER".
User-Agent: PolycomSoundPointIP-SPIP_300-UA/1.4.1.
Authorization: Digest username="userid", realm="ourdomain.com",
nonce="4296dae8877bf0f3f27488cc28d24e60fe4f6ca3",
uri="sip:ourdomain.com",
response="a0bcf66d87eaf62a80beb1c975af3074", algorithm=MD5.
Max-Forwards: 70.
Expires: 3600.
Content-Length: 0.
:-)
g-)
Juha Heinanen wrote:
Greger V. Teigre writes:
That's strange. We are using some Polycom 300
and they work ok. No
STUN support and sometimes a very erratic registration pattern, but
except from that, they seem to perform ok. They interoperate with
sipuras, grandstreams, sjphone, cisco gw, xlite, etc.
polycom phones were sent to us for testing by polycom dealer in
finland. perhaps their software version was not current, but when we
complained, no newer version was supplied. does yours support digest
authentication of register and other requests and place callee's
hostname (not ip address) in request uri?
-- juha