fanyapeng/boghe

Register message without uri and user of From and To header and user of Contact header

Opened this issue · 1 comments

What steps will reproduce the problem?
1.Installation Boghe IMS client 
2.Sending Register message without uri and user of from and To and contact 
header.
3.

What is the expected output? What do you see instead?
Adding URI and USER of From and To and Contact header.


What version of the product are you using? On what operating system?
Boghe IMS clien v 2.0.186.1013

Please provide any additional information below.
REGISTER sip:acme.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.57:57200;branch=z9hG4bK-2037152;rport
From: <sip:>;tag=2045798
To: <sip:>
Contact: 
<sip:(null)@192.168.1.57:57200;transport=udp>;expires=600000;+g.oma.sip-im;langu
age="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio;+g.3gpp.icsi-ref="ur
n%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp.cs-voice
Call-ID: dabd3645-7723-ffee-6775-4990ca80889e
CSeq: 3522 REGISTER
Content-Length: 0
Max-Forwards: 70
Authorization: Digest 
username="450061010001000@acme.com",realm="acme.com",nonce="",uri="sip:acme.com"
,response=""
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe-Win32/v2.0.186.1013
P-Preferred-Identity: <sip:>
Supported: path
Security-Client: 
ipsec-3gpp;alg=hmac-md5-96;ealg=aes-cbc;prot=ah;mod=trans;spi-c=4006499815;spi-s
=2629530413;port-c=57202;port-s=57201
Require: sec-agree
Proxy-Require: sec-agree





Original issue reported on code.google.com by bsj...@gmail.com on 16 Oct 2014 at 2:00

I saw the same thing until i changed the public identity to be 
sip:userpart@hostname, and the private identity to userpart.
I still am getting a null P-PreferredId which is getting rejected by openims.
Any ideas on why the P-Preferred header is null?

Original comment by tsec...@gmail.com on 23 Oct 2014 at 12:43