[SIP Beyond VoIP] Robustness of Sylk-Server

venu Y toyvenu at gmail.com
Fri Nov 2 13:45:28 CET 2012


Hi Anil,

Here is the sample flow from RFC 4975.
For initial dummy send

Byte-Range should be 1-0/0
To-Path and From-Path should be extracted from SIP signalling.

MSRP d93kswow SEND
To-Path: msrp://bob.example.com:8888/9di4eae923wzd;tcp
From-Path: msrp://alicepc.example.com:7777/iau39soe2843z;tcp
Message-ID: 12339sdqwer
Byte-Range: 1-16/16
-------d93kswow$

On Fri, Nov 2, 2012 at 5:44 PM, Anil KARADAG <akaradag at netas.com.tr> wrote:

> Hi Venu,****
>
> ** **
>
> ** **
>
> SIP INVITE sdp part includes the below lines.  Is that enough? If your
> answer is no, please provide a sample context. ****
>
> ** **
>
> ** **
>
> a=path:msrp://[local_ip]:2855/[call_number];tcp****
>
> a=accept-types:message/cpim text/* application/im-iscomposing+xml****
>
> a=accept-wrapped-types:*****
>
> a=setup:active****
>
> ** **
>
> ** **
>
> thanks for your help****
>
> ** **
>
> *From:* sipbeyondvoip-bounces at lists.ag-projects.com [mailto:
> sipbeyondvoip-bounces at lists.ag-projects.com] *On Behalf Of *venu Y
> *Sent:* Friday, November 02, 2012 12:13 PM
> *To:* Saúl Ibarra Corretgé
> *Cc:* sipbeyondvoip at lists.ag-projects.com
>
> *Subject:* Re: [SIP Beyond VoIP] Robustness of Sylk-Server****
>
> ** **
>
> We need to send initial MSRP message after TCP connection establishment.**
> **
>
> ** **
>
> For this you need some a= attributes from SDP. ****
>
> ** **
>
> Regards****
>
> -Venu****
>
> On Fri, Nov 2, 2012 at 2:27 PM, Saúl Ibarra Corretgé <saul at ag-projects.com>
> wrote:****
>
> Hi,****
>
>
> On Nov 2, 2012, at 9:48 AM, Onur DOLU wrote:
>
> > Thanks Saul,
> > We are aware of why sessions are terminated where we do not establish
> media path.
> > It is good to know that, "it is chosen according to the standart."
> >
> > What we are trying to do is,
> > First, making traffic only for sip sessions handling****
>
> This test is meaningless, all calls have media. Whatever the results would
> be, they don't resemble reality.****
>
>
> > Then, making traffic for both sip signaling and media path.
> >
> > We will try adding a simple application for creating tcp connection with
> the port that is received a=path in 200 OK.****
>
> That won't work. After establishing the TCP connection the connection
> needs to be 'bound' at the MSRP level, which means either sending or
> replying to an MSRP empty SEND chunk. There is also a keepalive process
> using the same mechanism during the call.****
>
>
> > If you have any workaround recommendation, it would be very helpful till
> we implement that dummy tcp socket application embedded into our sipp
> script.
> >****
>
> You need a proper MSRP client to test this, I see no other way around it.*
> ***
>
>
>
> Regards,
>
> --
> Saúl Ibarra Corretgé
> AG Projects
>
>
>
> _______________________________________________
> SIPBeyondVoIP mailing list
> SIPBeyondVoIP at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip****
>
>
>
> ****
>
> ** **
>
> --
> With Regards****
>
> Venu****
>
> 93484 89945****
>
> toyvenu at gmail.com****
>
> ** **
>



-- 
With Regards
Venu
93484 89945
toyvenu at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/sipbeyondvoip/attachments/20121102/53fc81ca/attachment-0001.html>


More information about the SIPBeyondVoIP mailing list