Getting bad request while trying to send Notify with a body

BN
Biswaranjan Nayak
Mon, Oct 8, 2018 6:23 AM

Dear Team,

I'm trying to send NOTIFY request with a body (name1: val1), but library
treated as (400 Bad Request).

Can anyone please help me out of this scenario ?

11:42:03.516 sip_endpoint.c  Processing incoming message: Request msg
NOTIFY/cseq=102 (rdata012ADFE4)

11:42:03.517  pjsua_core.c  .RX 620 bytes Request msg NOTIFY/cseq=102
(rdata012ADFE4) from UDP 172.16.3.183:5060:

NOTIFY sip:1803@192.168.153.12:60601;ob SIP/2.0

Via: SIP/2.0/UDP 172.16.3.183:5060;branch=z9hG4bK0a14e378

Max-Forwards: 70

From: "asterisk" sip:asterisk@172.16.3.183;tag=as11233e5f

To: sip:1803@192.168.153.12:60601;ob

Contact: sip:asterisk@172.16.3.183:5060

Call-ID: 602061684bc7c2d60d21550c73aefec0@172.16.3.183:5060

CSeq: 102 NOTIFY

User-Agent: Asterisk PBX certified/13.13-cert8

Date: Wed, 03 Oct 2018 06:12:02 GMT

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO,
PUBLISH, MESSAGE

Supported: replaces, timer

Subscription-State: terminated

name1: val1

Content-Length: 0

--end msg--

11:42:03.518      endpoint  .Response msg 400/NOTIFY/cseq=102
(tdta012A27D4) created

11:42:03.519  sip_resolve.c  .Target '172.16.3.183:5060' type=UDP resolved
to '172.16.3.183:5060' type=UDP (UDP transport)

11:42:03.519  pjsua_core.c  .TX 354 bytes Response msg 400/NOTIFY/cseq=102
(tdta012A27D4) to UDP 172.16.3.183:5060:

SIP/2.0 400 Bad Request

Via: SIP/2.0/UDP
172.16.3.183:5060;received=172.16.3.183;branch=z9hG4bK0a14e378

Call-ID: 602061684bc7c2d60d21550c73aefec0@172.16.3.183:5060

From: "asterisk" sip:asterisk@172.16.3.183;tag=as11233e5f

To: sip:1803@192.168.153.12;ob;tag=z9hG4bK0a14e378

CSeq: 102 NOTIFY

User-Agent: PJSUA v2.7.1/win32

Content-Length:  0

Thanks & Regards

Biswaranjan Nayak

Dear Team, I'm trying to send NOTIFY request with a body (name1: val1), but library treated as (400 Bad Request). Can anyone please help me out of this scenario ? 11:42:03.516 sip_endpoint.c Processing incoming message: Request msg NOTIFY/cseq=102 (rdata012ADFE4) 11:42:03.517 pjsua_core.c .RX 620 bytes Request msg NOTIFY/cseq=102 (rdata012ADFE4) from UDP 172.16.3.183:5060: NOTIFY sip:1803@192.168.153.12:60601;ob SIP/2.0 Via: SIP/2.0/UDP 172.16.3.183:5060;branch=z9hG4bK0a14e378 Max-Forwards: 70 From: "asterisk" <sip:asterisk@172.16.3.183>;tag=as11233e5f To: <sip:1803@192.168.153.12:60601;ob> Contact: <sip:asterisk@172.16.3.183:5060> Call-ID: 602061684bc7c2d60d21550c73aefec0@172.16.3.183:5060 CSeq: 102 NOTIFY User-Agent: Asterisk PBX certified/13.13-cert8 Date: Wed, 03 Oct 2018 06:12:02 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Subscription-State: terminated name1: val1 Content-Length: 0 --end msg-- 11:42:03.518 endpoint .Response msg 400/NOTIFY/cseq=102 (tdta012A27D4) created 11:42:03.519 sip_resolve.c .Target '172.16.3.183:5060' type=UDP resolved to '172.16.3.183:5060' type=UDP (UDP transport) 11:42:03.519 pjsua_core.c .TX 354 bytes Response msg 400/NOTIFY/cseq=102 (tdta012A27D4) to UDP 172.16.3.183:5060: SIP/2.0 400 Bad Request Via: SIP/2.0/UDP 172.16.3.183:5060;received=172.16.3.183;branch=z9hG4bK0a14e378 Call-ID: 602061684bc7c2d60d21550c73aefec0@172.16.3.183:5060 From: "asterisk" <sip:asterisk@172.16.3.183>;tag=as11233e5f To: <sip:1803@192.168.153.12;ob>;tag=z9hG4bK0a14e378 CSeq: 102 NOTIFY User-Agent: PJSUA v2.7.1/win32 Content-Length: 0 Thanks & Regards Biswaranjan Nayak