VoIP Mailing List Archives

[lukasz at czerpak.eu]

Hi,

I have some troubles with provider configuration. The are warnings in logs:

2009-03-19 19:02:48 [WARNING] mod_sofia.c:739 sofia_read_frame() We were
told to use ptime 20 but what they meant to say was 40

This issue has so far been identified to happen on the following broken
platforms/devices:

Linksys/Sipura aka Cisco


ShoreTel


Sonus/L3


We will try to fix it but some of the devices on this list are so broken
who knows what will happen..

My provider uses SER and Cisco hardware (Cisco-SIPGateway/IOS-12.x).

Moreover, above warning appears only when someone calls to FreeSWITCH
(voice quality is poor) - connection from FreeSWITCH works without any
warnings and has perfect quality.

Other my providers works perfect.

Is there any solution of this problem?

regards,
Lukasz



_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[brian at freeswitch.org]

Try:


<param name="inbound-codec-negotiation" value="scrooge"/>

/b

On Mar 19, 2009, at 1:22 PM, �ukasz Czerpak wrote:

[lukasz at czerpak.eu]

Brian West wrote:

[brian at freeswitch.org]

what rev are you on?

/b

On Mar 19, 2009, at 1:52 PM, �ukasz Czerpak wrote:

[kristian.kielhofner at...]

Hi,

This is a known issue with some of these platforms but for
completeness can you send the actual SDP?

2009/3/19 £ukasz Czerpak <lukasz@czerpak.eu>:

[lukasz at czerpak.eu]

Kristian Kielhofner wrote:

[brian at freeswitch.org]

Well you can't have ptime 60 one way and 20 the other it just won't work. Also I can't even think that this illegal codec was even tested at 60ms... Try it with ulaw and see what it does. or only allow G729@60i and see what it does.



/b

On Mar 19, 2009, at 2:20 PM, £ukasz Czerpak wrote:

[lukasz at czerpak.eu]

Brian West wrote:

[lukasz at czerpak.eu]

Brian West wrote:

[brian at freeswitch.org]

The issue I seen was they invite to you with NO ptime which indicates
20ms, they should invite with ptime:60 if they want 60.

/b

On Mar 19, 2009, at 3:06 PM, �ukasz Czerpak wrote:

[lukasz at czerpak.eu]

Brian West wrote:

[brian at freeswitch.org]

Well you said you were using G.729 for testing... when you're clearly
not... but I told you already how to fix it... for that IP or peer
G729@60i

/b

On Mar 19, 2009, at 4:03 PM, �ukasz Czerpak wrote:

[lukasz at czerpak.eu]

Brian West pisze:

[pablosaro at gmail.com]

I am not a Cisco expert, but as far as I know packetization period is
configurable in Cisco. When you specify the codec for a dial peer, you
can set up the ptime value in milliseconds. This is an optional
argument in the Cisco command line and what happens when providers
don't specify it is that your end assumes a convenient or default
ptime value, that probably don't match with far end default... A
solution would be to figure out what is the convenient value for an
individual provider and set up FS to match it, or suggest your
provider to specify a ptime in the first request.
By the way, Cisco supports 10, 20, 30, 40, 50 and 60 as ptime values
for codecs G.729, G.729A, G.729B and G.729AB.

Pablo


2009/3/20 £ukasz Czerpak <lukasz@czerpak.eu>:

[alhakeem at gmail.com]

The pvalue of the originator overrides whatever you might have configured on
Cisco GW.

-----Original Message-----
From: freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Pablo
Hernan Saro
Sent: 21 March 2009 03:16
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] ptime problem with provider (Cisco hardware)

I am not a Cisco expert, but as far as I know packetization period is
configurable in Cisco. When you specify the codec for a dial peer, you can
set up the ptime value in milliseconds. This is an optional argument in the
Cisco command line and what happens when providers don't specify it is that
your end assumes a convenient or default ptime value, that probably don't
match with far end default... A solution would be to figure out what is the
convenient value for an individual provider and set up FS to match it, or
suggest your provider to specify a ptime in the first request.
By the way, Cisco supports 10, 20, 30, 40, 50 and 60 as ptime values for
codecs G.729, G.729A, G.729B and G.729AB.

Pablo


2009/3/20 £ukasz Czerpak <lukasz@czerpak.eu>: