Skip to content

malformed authorization header #813

@YoungDopeGeek

Description

@YoungDopeGeek

hello in sipp when i trying to use the AKAV1-MD5 alg for authenticate
sipp gives me an malformed header, i think can't parse correctly the parameters and it tries to put first of line the first parameter value(each parameter is set to first parameter)

it gives me this message format

----------------------------------------------- 2025-11-11 15:05:14.237817
UDP message sent (777 bytes):

REGISTER sip:ims.mnc001.mcc001.3gppnetwork.org SIP/2.0
User-Agent: SIPp IMS Test
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
Expires: 3000

[email protected][authentication username= aka_K=465B5CE8B199B49FAA5F0A2EE238A6BC aka_OP=00000000000000000000000000000000 aka_AMF=8000]

P-Access-Network-Info: IEEE-802.11;i-wlan-node-id=9cc7a608a31d
Contact: <sip:[email protected]:9977>;Expires=9000
From: <sip:[email protected]>;tag=1
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 2 REGISTER
Max-Forwards: 70
Via: SIP/2.0/UDP 172.22.0.1:9977;branch=z9hG4bK-106442-1-3;transport=UDP
Content-Length: 0

and lines below is my request in xml scenario

<send>

REGISTER sip:[field1] SIP/2.0
User-Agent: SIPp IMS Test
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,INFO,REFER,NOTIFY,MESSAGE,PRACK
Expires: 3000
[authentication username=[field2] aka_K=[field3] aka_OP=[field4] aka_AMF=[field5]] <- auth header with format specified in sipp doc ->
P-Access-Network-Info: IEEE-802.11;i-wlan-node-id=9cc7a608a31d
Contact: <sip:[field0]@[local_ip]:[local_port]>;Expires=9000
From: <sip:[field2]>;tag=[call_number]
To: <sip:[field2]>
Call-ID: [call_id]
CSeq: 2 REGISTER
Max-Forwards: 70
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch];transport=[transport]
Content-Length: 0

</send>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions