I read about problems that the CP-7912G with SIP Firmware has.
Which of the following problems are due to the SIP Firmware?
First,
the phone reports a "Host to long" when the phone is called and in the via, to, from fields use a host that is longer than about 32 characters.
e.g
Via: SIP/2.0/UDP gmxgmx.sip.mgc.voip.telekomika.com:5060
;received=195.71.9.100;branch=z9hG4bKterm-128f1c-+4116085633483-+414026746374
f: +4116085633483 <sip:+4116085633483@gmxgmx.sip.mgc.voip.telekomika.com;user=phone>;tag=794284950
t: +414026746374 <sip:+414026746374@gmxgmx.interconnect.sip.voip.telekomika.com;user=phone>
Second,
two colons in Cancel Request-URI (Rfc3261)
CANCEL sip::80.95.252.24:5070;avp=B50DCA SIP/2.0
Third
missformed CANCEL Requests. (The Request-URI, Call-ID, To, the numeric part of CSeq, and From header
fields in the CANCEL request MUST be identical to those in the
request being cancelled, including tags. (Rfc3261 9.1))
The Repest-URI of the Cancel has nothing to do with that in the INVITE
e.g.
INVITE sip:01608438483@sip.carpo.de;user=phone SIP/2.0
CANCEL sip::80.95.252.14:5070;avp=B50DCA SIP/2.0
the new CANCEL Request-URI was taken from the topmost Record-Route.
SIP/2.0 183 Sitzungsfortschritt
Record-Route:
<sip:80.95.252.14:5070;avp=B50DCABydHBwcm94eQMAeWVz;lr=on>
Record-Route: <sip:80.95.252.5;lr=on>
or
INVITE sip:23200302@sip.carpo.de;user=phone SIP/2.0
CANCEL sip:wa.mayer@84.150.187.204:5062 SIP/2.0
taken perhaps from the SIP/2.0 180 Contact
Contact: <sip:wa.mayer at 84.150.187.204:5062;transport=udp>
Fourth
the NATIP does not support a FQDN so no DYNDNS is possible. As there is no STUN feature, a FQDN would be necessary.
Fifth
the DirectoriesURL and ServicesURL Parameter, that can be set through a Profile, don't work.
Apart from other bugs, what is true from these problem reports I found?
As it seems the phone is not SIP compliant?
And therefor can't be used with for example SER?
