cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1402
Views
0
Helpful
1
Replies

SPA112 bug: P-Station-Name sent twice in REGISTER

Dan Lukes
VIP Alumni
VIP Alumni

Configured Station Name is published by SPA112 device in REGISTER's P-Station-Name header. See catched packed bellow (Station Name=Ustredna TEST)

REGISTER sip:10.B.C.1:5060 SIP/2.0

From: "6018" <sip:DEV-6018@10.B.C.1>;tag=ce2aebb4a48624fbo0

To: "6018" <sip:DEV-6018@10.B.C.1>

Authorization: Digest username="DEV-6018",realm="test.sip.L.M.cz",nonce="141c3772",

   uri="sip:10.P.Q.1:5060",algorithm=MD5,response="d6a320488f37acb05ad8eef315f6e7fc"

Contact: "6018" <sip:DEV-6018@10.X.Y.11:5060>;expires=3600

P-Station-Name: ;mac=c4........90; sn=CCQ......LR

User-Agent: Cisco/SPA112-1.3.2(009)

P-Station-Name: Ustredna TEST ;mac=c4........90; display="Ustredna TEST"; sn=CCQ......LR

...

Unfortunatelly, the header is sent twice in REGISTER. The first one without Station Name, the second with Station Name. As far as I know, the behavior how to interpret multiple P-Station-Name headers in one packet is not defined. So it may confuse PBX and cause unpredictable results. I assume it's bug, not intentional feature.

It would be nice if such bug will be patched ...

Note, the catched packet has been sent from device with unreleased firmware 1.3.2(009) but the same behavior has been observer on 1.3.1.

1 Reply 1

nseto
Level 6
Level 6

This has been entered as a bug, ID is CSCuf90879 and will be addressed in a future release.  Thanks.