---

---

The above scenario is good for this.

---

Posted by HamidAliKhan

SIP is a request/response protocol. Request and Response have the basic structure.
Hereafter a example of SIP Request/Response message.

Request:
INVITINVITE sip:UserB@aaa.com SIP/2.0
Via: SIP/2.0/UDP bbb.com:5060
From: BigGuy ;tag=123
To: LittleGuy
Call-ID: 12345600@bbb.com
CSeq: 1 INVITE
Subject: SIP message
Contact: BigGuy
Content-Type: application/sdp
Content-Length: 147
Request Payload
SDP (RFC2327): “receive RTP G.711-
encoded audio at 100.101.102.103:49172”
v=0
o=UserA 2890844526 2890844526 IN IP4 bbb.com
s=Session SDP
c=IN IP4 100.101.102.103
t=0 0
m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000

Response
SIP/2.0 200 OK
Via: SIP/2.0/UDP here.com:5060
From: BigGuy ;tag=123
To: LittleGuy ;tag=65a35
Call-ID: 12345600@bbb.com
CSeq: 1 INVITE
Subject: SIP message
Contact: LittleGuy
Content-Type: application/sdp
Content-Length: 134
Response PayLoad
v=0
o=UserB 2890844527 2890844527 IN IP4 there.com
s=Session SDP
c=IN IP4 110.111.112.113
t=0 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000

you can develop some software that creates all possible SIP messages INVITE, PRACK....
the point is to respect SIP protocol RFC.

---

Posted by snjysanjay05