Thanks Paul for your great suggestions. Since, I don't want to add traffic
to network, so I don't want to use a separate set of SIP MESSAGE
request/response. Based on our requirements, I find your suggestion of
Content-ID header field option being really suitable. I am putting the
request/response
On 4/13/19 4:43 PM, abhishek jain wrote:
Thanks Paul for your quick response on a Saturday. I really appreciate.
I am wondering how to implement below without introducing another pair
of SIP request/response, if you could suggest that would be great with
SIP compliance -
1. My server sending
Thanks Paul for your quick response on a Saturday. I really appreciate.
I am wondering how to implement below without introducing another pair of
SIP request/response, if you could suggest that would be great with SIP
compliance -
1. My server sending some configurations to client using SIP MESSAG
On 4/13/19 3:58 PM, abhishek jain wrote:
Hi,
Can a Sip Response (to a Non-Dialog creating SIP Request) contain a body ?
I would appreciate a quick response.
Sometimes. The rules vary depending on the type of message.
But not for MESSAGE. RFC3480 (section 7) says:
A 2xx response to a MESSA
>
> Hi,
> Can a Sip Response (to a Non-Dialog creating SIP Request) contain a body ?
> I would appreciate a quick response.
>
> For example -
> *Server to **Client **:*
> MESSAGE
> :
>
> Content-Type: application/chat-info+xml
>
> Content-Length: ...
>
>
>
>
> :
>
>
>
>
> *Client to S
