[Spce-user] Fwd: Packet Size

qabane me qabaneitsolutions at gmail.com
Tue Sep 18 03:24:12 EDT 2018


Hi Daniel

I have entered it like that now. It does appear that in both cases the
result is the same and the b=AS:80 is removed from SDP when passed down.
But either way, it still doesn't appear to work. the SDP sent to upstream
from Sipwise is:
[image: image.png]
We have set the ptime to that peer to 20 under media transcoding options.

We receive back:
[image: image.png]

Then passed to sip proxy (127.0.0.1:5060 >>> 127.0.0.5080) it appears that
the line filter to take out the b:AS:80 works fine

[image: image.png]
But once RTP starts it looks like that ptime of 20 is not being honoured by
sipwise as the actual packet size of RTP sent indicates a ptime of 40
whereas the packetsize of RTP received from upstream is indeed 20.

We are only observing this when that b= parameter is present by the looks
of it.



On Mon, Sep 17, 2018 at 5:05 PM Daniel Grotti <dgrotti at sipwise.com> wrote:

> Hi,
> it should look like:
>
>
> sdp_line_filter:
>       enable: yes
>       remove_line_startswith:
>       - b=
>
>
> in order to remove lines starting with "b=".
>
> Cheers,
>
> --
> Daniel Grotti
> Head of Customer Support
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
>
> Office: +43(0)130120332
> Email: dgrotti at sipwise.com
> Website: https://www.sipwise.com
>
> On 09/11/2018 12:31 PM, qabane me wrote:
>
> Hi
>
> I have played a bit more with this and found in config.yml:
>
>   sdp_line_filter:
>       enable: yes
>       remove_line_startswith: [b]
>  (I added the yes and the b)
>
> This indeed filters out that line - sngrep shows that the lb does not pass
> it to the proxy. However, the behaviour remains the same. When a call comes
> in with a ptime of 60, sipwise sends it on to the peer with a ptime of 40.
> My guess is that it picks 40 based on the max bandwidth of 80? I had hoped
> that by filtering that line from the sdp it would not do this anymore but
> no joy there.
>
> Any ideas?
>
> ---------- Forwarded message ---------
> From: qabane me <qabaneitsolutions at gmail.com>
> Date: Thu, Sep 6, 2018 at 11:55 AM
> Subject: Fwd: Packet Size
> To: <spce-user at lists.sipwise.com>
>
>
> Ok I am not entirely correct. It does seem to work - but not to one
> carrier. The difference is that this carrier responds with b=AS:80. As a
> result (and I am only assuming it is as a result of that flag) the packet
> size we are sending out is 40 which results in one way audio. This is
> despite the fact that have set the ptime to 20 and despite the fact that
> there is a maxptime:20 in their response.
>
> [image: image.png]
>
> ---------- Forwarded message ---------
> From: qabane me <qabaneitsolutions at gmail.com>
> Date: Thu, Sep 6, 2018 at 11:20 AM
> Subject: Packet Size
> To: <spce-user at lists.sipwise.com>
>
>
> Hi
>
> As part of our testing of MR6.4.1 we are playing with repackatisation. We
> have set, on a peer level, a packet size of 20. Then we send a call from a
> PBX with a ptime of 60. I had expected this to be repacketised to 20 going
> upstream but that does not seem to work.
>
> Am I misunderstanding this or is something not working?
>
> Cheers
> Theo
>
>
> _______________________________________________
> Spce-user mailing listSpce-user at lists.sipwise.comhttps://lists.sipwise.com/listinfo/spce-user
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180918/55b5b368/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 3710 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180918/55b5b368/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 6480 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180918/55b5b368/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 3378 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180918/55b5b368/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 3136 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180918/55b5b368/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 3710 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180918/55b5b368/attachment-0009.png>


More information about the Spce-user mailing list