Vonage: What DSCP or ToS Values?

Toggle sidebar Toggle sidebar
G

Guest

Guest
Archived from groups: comp.dcom.voice-over-ip (More info?)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Has anyone figured out what Ip Precendence/ToS/DSCP values the
vonage ATA186 bearer traffic uses? I want to map the bearer
packets to a LLQ and was expecting them to be "ip precedence 5"
but that does not work. The call setup messages are working via
"ip precendence 3".

Anyone know the bearer value?

thanks

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQSG9R+HzPuqqaV5HEQLb3gCfcdaIr8lR2twOZk+VwlAVIF4KWLUAoLLF
6WUUx+YiQgOuleJX48Sp8pEp
=haCD
-----END PGP SIGNATURE-----
 
Archived from groups: comp.dcom.voice-over-ip (More info?)

Cheetoh wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Has anyone figured out what Ip Precendence/ToS/DSCP values the
> vonage ATA186 bearer traffic uses? I want to map the bearer
> packets to a LLQ and was expecting them to be "ip precedence 5"
> but that does not work. The call setup messages are working via
> "ip precendence 3".
>
> Anyone know the bearer value?
>
>

You mean the RTP packets that actually carry th g.711 encoded voice
traffic? Dunno. Why not just run ethereal and look at the packates and
see for yourself?

(you got me curious - i'm going to do exactly that with my vonage ata186
when I get home tonight)
 
Archived from groups: comp.dcom.voice-over-ip (More info?)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi,

Yes, I mean the RTP bearer stream for the G.711 packets. Working on
getting the Ethereal traces too but
thought someone might have already done it...

thx

"T. Sean Weintz" <strap@hanh-ct.org> wrote in message
news:10i4iiolgve2r26@news.supernews.com...
> Cheetoh wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Has anyone figured out what Ip Precendence/ToS/DSCP values the
> > vonage ATA186 bearer traffic uses? I want to map the bearer
> > packets to a LLQ and was expecting them to be "ip precedence 5"
> > but that does not work. The call setup messages are working via
> > "ip precendence 3".
> >
> > Anyone know the bearer value?
> >
> >
>
> You mean the RTP packets that actually carry th g.711 encoded voice
> traffic? Dunno. Why not just run ethereal and look at the packates
> and see for yourself?
>
> (you got me curious - i'm going to do exactly that with my vonage
> ata186 when I get home tonight)

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQSL2yOHzPuqqaV5HEQLclQCg33400+zoq/Cp6yiGEknkWB1Yf6kAn26D
VgIhuIQW4MXGWrXvWcnggxyr
=beuj
-----END PGP SIGNATURE-----
 
Archived from groups: comp.dcom.voice-over-ip (More info?)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So it turns out that the current firmware Vonage is using on the
Cisco ATA186's has a bug that puts a 0x0
value in the IP Precedence field, so instead of sending voip bearer
packets with an IP Precendence 5 they
are sent with 0, like all data. I have worked with them and they
have loaded a test image and it works
like a champ now and my LLQ is working great in case any one else is
trying to do this...

LLQ-router# show voice queuing

Ethernet1

Service-policy output: shape

Class-map: class-default (match-any)
365625 packets, 66899306 bytes
30 second offered rate 591000 bps, drop rate 0 bps
Match: any
Traffic Shaping
Target/Average Byte Sustain Excess Interval
Increment
Rate Limit bits/int bits/int (ms)
(bytes)
1100000/1100000 6600 26400 26400 24 3300


Adapt Queue Packets Bytes Packets Bytes
Shaping
Active Depth Delayed Delayed
Active
- 3 361289 66615027 11338 13704219 yes

Service-policy : LLQ

Class-map: call-setup (match-all)
5675 packets, 1804013 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip precedence 3
Queueing
Output Queue: Conversation 73
Bandwidth 5 (%)
Bandwidth 55 (kbps) Max Threshold 64 (packets)
(pkts matched/bytes matched) 25/8990
(depth/total drops/no-buffer drops) 0/0/0

Class-map: voice (match-all)
129981 packets, 18261798 bytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip precedence 5
Queueing
Strict Priority
Output Queue: Conversation 72
Bandwidth 165 (kbps) Burst 4125 (Bytes)
(pkts matched/bytes matched) 1349/279958
(total drops/bytes drops) 0/0

Class-map: class-default (match-any)
229969 packets, 46833495 bytes
30 second offered rate 592000 bps, drop rate 0 bps
Match: any
Queueing
Flow Based Fair Queueing
Maximum Number of Hashed Queues 64
(total queued/total drops/no-buffer drops) 3/0/0

"Cheetoh" <stelee1969@charter.net> wrote in message
news:10i3fc5h0iplq93@corp.supernews.com...
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Has anyone figured out what Ip Precendence/ToS/DSCP values the
> vonage ATA186 bearer traffic uses? I want to map the bearer
> packets to a LLQ and was expecting them to be "ip precedence 5"
> but that does not work. The call setup messages are working via
> "ip precendence 3".
>
> Anyone know the bearer value?
>
> thanks
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.0.3
>
> iQA/AwUBQSG9R+HzPuqqaV5HEQLb3gCfcdaIr8lR2twOZk+VwlAVIF4KWLUAoLLF
> 6WUUx+YiQgOuleJX48Sp8pEp
> =haCD
> -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQSbtDuHzPuqqaV5HEQLOqQCfbxF2vv73/XiGHk8YZ6Qbrzvn7wwAnj43
7bmg9aHv2dgvjNntxWDl0HG5
=9oY4
-----END PGP SIGNATURE-----
 
Archived from groups: comp.dcom.voice-over-ip (More info?)

On Sat, 21 Aug 2004 06:34:56 GMT, Cheetoh wrote in
news:10idr89jr1ev410@corp.supernews.com:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> So it turns out that the current firmware Vonage is using
> on the Cisco ATA186's has a bug that puts a 0x0
> value in the IP Precedence field, so instead of sending
> voip bearer packets with an IP Precendence 5 they
> are sent with 0, like all data. I have worked with them
> and they have loaded a test image and it works
> like a champ now and my LLQ is working great in case any
> one else is trying to do this...
>
> LLQ-router# show voice queuing
>
> Ethernet1
>
> Service-policy output: shape
>
> Class-map: class-default (match-any)
> 365625 packets, 66899306 bytes
> 30 second offered rate 591000 bps, drop rate 0 bps
> Match: any
> Traffic Shaping
> Target/Average Byte Sustain Excess
> Interval
> Increment
> Rate Limit bits/int bits/int (ms)
> (bytes)
> 1100000/1100000 6600 26400 26400 24
> 3300
>
>
> Adapt Queue Packets Bytes Packets
> Bytes
> Shaping
> Active Depth Delayed
> Delayed
> Active
> - 3 361289 66615027 11338
> 13704219 yes
>
> Service-policy : LLQ
>
> Class-map: call-setup (match-all)
> 5675 packets, 1804013 bytes
> 30 second offered rate 0 bps, drop rate 0 bps
> Match: ip precedence 3
> Queueing
> Output Queue: Conversation 73
> Bandwidth 5 (%)
> Bandwidth 55 (kbps) Max Threshold 64 (packets)
> (pkts matched/bytes matched) 25/8990
> (depth/total drops/no-buffer drops) 0/0/0
>
> Class-map: voice (match-all)
> 129981 packets, 18261798 bytes
> 30 second offered rate 0 bps, drop rate 0 bps
> Match: ip precedence 5
> Queueing
> Strict Priority
> Output Queue: Conversation 72
> Bandwidth 165 (kbps) Burst 4125 (Bytes)
> (pkts matched/bytes matched) 1349/279958
> (total drops/bytes drops) 0/0
>
> Class-map: class-default (match-any)
> 229969 packets, 46833495 bytes
> 30 second offered rate 592000 bps, drop rate 0
> bps Match: any
> Queueing
> Flow Based Fair Queueing
> Maximum Number of Hashed Queues 64
> (total queued/total drops/no-buffer drops) 3/0/0

So, are they going to make the flash available to whoever
wants/needs it? Is there a good point of contact for firmware
issues?

Flatus
 
Archived from groups: comp.dcom.voice-over-ip (More info?)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

support@vonage.com is all I used via email and they responded...

"Flatus Ohlfahrt" <flatus@militaryretired.us> wrote in message
news:Xns954C88B73CAEAflatusmilitaryret@130.133.1.4...
> On Sat, 21 Aug 2004 06:34:56 GMT, Cheetoh wrote in
> news:10idr89jr1ev410@corp.supernews.com:
>
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > So it turns out that the current firmware Vonage is using
> > on the Cisco ATA186's has a bug that puts a 0x0
> > value in the IP Precedence field, so instead of sending
> > voip bearer packets with an IP Precendence 5 they
> > are sent with 0, like all data. I have worked with them
> > and they have loaded a test image and it works
> > like a champ now and my LLQ is working great in case any
> > one else is trying to do this...
> >
> > LLQ-router# show voice queuing
> >
> > Ethernet1
> >
> > Service-policy output: shape
> >
> > Class-map: class-default (match-any)
> > 365625 packets, 66899306 bytes
> > 30 second offered rate 591000 bps, drop rate 0 bps
> > Match: any
> > Traffic Shaping
> > Target/Average Byte Sustain Excess
> > Interval
> > Increment
> > Rate Limit bits/int bits/int (ms)
> > (bytes)
> > 1100000/1100000 6600 26400 26400 24
> > 3300
> >
> >
> > Adapt Queue Packets Bytes Packets
> > Bytes
> > Shaping
> > Active Depth Delayed
> > Delayed
> > Active
> > - 3 361289 66615027 11338
> > 13704219 yes
> >
> > Service-policy : LLQ
> >
> > Class-map: call-setup (match-all)
> > 5675 packets, 1804013 bytes
> > 30 second offered rate 0 bps, drop rate 0 bps
> > Match: ip precedence 3
> > Queueing
> > Output Queue: Conversation 73
> > Bandwidth 5 (%)
> > Bandwidth 55 (kbps) Max Threshold 64 (packets)
> > (pkts matched/bytes matched) 25/8990
> > (depth/total drops/no-buffer drops) 0/0/0
> >
> > Class-map: voice (match-all)
> > 129981 packets, 18261798 bytes
> > 30 second offered rate 0 bps, drop rate 0 bps
> > Match: ip precedence 5
> > Queueing
> > Strict Priority
> > Output Queue: Conversation 72
> > Bandwidth 165 (kbps) Burst 4125 (Bytes)
> > (pkts matched/bytes matched) 1349/279958
> > (total drops/bytes drops) 0/0
> >
> > Class-map: class-default (match-any)
> > 229969 packets, 46833495 bytes
> > 30 second offered rate 592000 bps, drop rate 0
> > bps Match: any
> > Queueing
> > Flow Based Fair Queueing
> > Maximum Number of Hashed Queues 64
> > (total queued/total drops/no-buffer drops) 3/0/0
>
> So, are they going to make the flash available to whoever
> wants/needs it? Is there a good point of contact for firmware
> issues?
>
> Flatus

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQSeQ3OHzPuqqaV5HEQKRDACgzQT9pM7MlbTPNCbybWRIIrjQm7kAoLe2
G0mf7DEh0BdVFu2usYhQnZZU
=ceWK
-----END PGP SIGNATURE-----
 
Archived from groups: comp.dcom.voice-over-ip (More info?)

On Sat, 21 Aug 2004 18:13:50 GMT, Cheetoh wrote in
news:10if451diua58c8@corp.supernews.com:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> support@vonage.com is all I used via email and they
> responded...
>
> "Flatus Ohlfahrt" <flatus@militaryretired.us> wrote in
> message
> news:Xns954C88B73CAEAflatusmilitaryret@130.133.1.4...
>> On Sat, 21 Aug 2004 06:34:56 GMT, Cheetoh wrote in
>> news:10idr89jr1ev410@corp.supernews.com:
>>
>> >
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > So it turns out that the current firmware Vonage is
>> > using on the Cisco ATA186's has a bug that puts a 0x0
>> > value in the IP Precedence field, so instead of sending
>> > voip bearer packets with an IP Precendence 5 they
>> > are sent with 0, like all data. I have worked with them
>> > and they have loaded a test image and it works
>> > like a champ now and my LLQ is working great in case any
>> > one else is trying to do this...
>> >
>> > LLQ-router# show voice queuing
>> >
>> > Ethernet1
>> >
>> > Service-policy output: shape
>> >
>> > Class-map: class-default (match-any)
>> > 365625 packets, 66899306 bytes
>> > 30 second offered rate 591000 bps, drop rate 0 bps
>> > Match: any
>> > Traffic Shaping
>> > Target/Average Byte Sustain Excess
>> > Interval
>> > Increment
>> > Rate Limit bits/int bits/int
>> > (ms)
>> > (bytes)
>> > 1100000/1100000 6600 26400 26400
>> > 24
>> > 3300
>> >
>> >
>> > Adapt Queue Packets Bytes Packets
>> > Bytes
>> > Shaping
>> > Active Depth Delayed
>> > Delayed
>> > Active
>> > - 3 361289 66615027 11338
>> > 13704219 yes
>> >
>> > Service-policy : LLQ
>> >
>> > Class-map: call-setup (match-all)
>> > 5675 packets, 1804013 bytes
>> > 30 second offered rate 0 bps, drop rate 0 bps
>> > Match: ip precedence 3
>> > Queueing
>> > Output Queue: Conversation 73
>> > Bandwidth 5 (%)
>> > Bandwidth 55 (kbps) Max Threshold 64
>> > (packets) (pkts matched/bytes matched)
>> > 25/8990
>> > (depth/total drops/no-buffer drops) 0/0/0
>> >
>> > Class-map: voice (match-all)
>> > 129981 packets, 18261798 bytes
>> > 30 second offered rate 0 bps, drop rate 0 bps
>> > Match: ip precedence 5
>> > Queueing
>> > Strict Priority
>> > Output Queue: Conversation 72
>> > Bandwidth 165 (kbps) Burst 4125 (Bytes)
>> > (pkts matched/bytes matched) 1349/279958
>> > (total drops/bytes drops) 0/0
>> >
>> > Class-map: class-default (match-any)
>> > 229969 packets, 46833495 bytes
>> > 30 second offered rate 592000 bps, drop rate 0
>> > bps Match: any
>> > Queueing
>> > Flow Based Fair Queueing
>> > Maximum Number of Hashed Queues 64
>> > (total queued/total drops/no-buffer drops) 3/0/0
>>
>> So, are they going to make the flash available to whoever
>> wants/needs it? Is there a good point of contact for
>> firmware issues?
>>
>> Flatus
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 8.0.3
>
> iQA/AwUBQSeQ3OHzPuqqaV5HEQKRDACgzQT9pM7MlbTPNCbybWRIIrjQm7kA
> oLe2 G0mf7DEh0BdVFu2usYhQnZZU
>=ceWK
> -----END PGP SIGNATURE-----

Thanks for this. After your messages, I emailed them and was
told that they flashed my 186 with the new firmware this
morning.

Flatus
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom