From: Sergio Jimenez Arguedas (sejimenez@its.co.cr)
Date: Fri May 21 2004 - 23:59:50 GMT-3
Willian and Richard,
Thanks for your help,
Without RSVP it works fine!!! But when I applied RSVP the calls fail!!!
I used the cmd " incoming called-number xxx " with RSVP and it worked!!!
THANKS SO MUCH!!!
Q1: When do I need to use that command?
Sergio
Aditional Information:
R1#sh ip rsvp reservation
To From Pro DPort Sport Next Hop I/F Fi Serv
BPS
129.44.85.1 129.44.85.5 UDP 18228 16772 FF LOAD
24K
129.44.85.5 129.44.85.1 UDP 16772 18228 129.44.85.5 Et0/0 FF LOAD
24K
R1#csim start 5000
csim: called number = 5000, loop count = 1 ping count = 0
!
csim: loop = 1, failed = 0
csim: call attempted = 1, setup failed = 0, tone failed = 0
06:58:36: RSVP session 129.44.85.5_16502: Sending PATH message for
129.44.85.5 on interface Ethernet0/0
06:58:36: RSVP session 129.44.85.5_0: IP to 129.44.85.5 length=172
checksum=8DF5 TOS=0x00 (Ethernet0/0)
06:58:36: RSVP 129.44.85.5_4097-129.44.85.1_36337: message received from
129.44.85.5, TOS 0x0
06:58:36: RSVP 129.44.85.5_16502-129.44.85.1_16798: Received PATH Message
for 129.44.85.1(Ethernet0/0) from 129.44.85.5, rcv IP ttl=254
06:58:36: RSVP 129.44.85.5_16502-129.44.85.1_16798: End path:
129.44.85.5_16502->129.44.85.1_16798 17; Listener: 129.44.85.1_16798 17;
Event: 1
06:58:36: Creating (API) reservation (addr 62F20FD0) for dest 129.44.85.1
src 129.44.85.5 protocol 17, dest port 16798 src port 16502, idb NULL mode 1
06:58:36: Refreshing static reservation for dest 129.44.85.1 src 129.44.85.5
protocol 17, dest port 16798 src port 16502, idb NULL
06:58:36: RSVP 129.44.85.5_16502-129.44.85.1_16798: Static reservation is
new
06:58:36: RSVP-RESV: Locally created reservation. No admission/traffic
control needed
06:58:36: RSVP 129.44.85.5_16502-129.44.85.1_16798: start requesting 24 kbps
FF reservation for 129.44.85.5(16502) UDP-> 129.44.85.1(16798) on
Ethernet0/0 neighbor 129.44.85.5
06:58:36: RSVP 129.44.85.5_16502-129.44.85.1_16798: Sending RESV message
129.44.85.1(16798) <- 129.44.85.5(17:16502)
06:58:36: RSVP session 129.44.85.1_16798: send reservation to 129.44.85.5
about 129.44.85.1
06:58:36: RSVP session 129.44.85.1_0: IP to 129.44.85.5 length=96
checksum=EA0A TOS=0x00 (Ethernet0/0)
06:58:36: RSVP 129.44.85.5_4098-129.44.85.1_1220: message received from
129.44.85.5, TOS 0x0
06:58:36: RSVP 129.44.85.1_16798-129.44.85.5_16502: RESV message for
129.44.85.5 (Ethernet0/0) from 129.44.85.5
06:58:36: RSVP session 129.44.85.5_16502: Reservation is new
06:58:36: RSVP session 129.44.85.5_16502: send reservation confirm to
129.44.85.5 about 129.44.85.5
06:58:36: RSVP session 129.44.85.5_0: IP to 129.44.85.5 length=96
checksum=7C04 TOS=0x00 (Ethernet0/0)
06:58:39: RSVP 129.44.85.1_16798-129.44.85.5_16502: remove sender host PATH
129.44.85.5(16502) <- 129.44.85.1(17:16798)
06:58:39: RSVP 129.44.85.1_16798-129.44.85.5_16502: remove Ethernet0/0 RESV
129.44.85.5(16502) <- 129.44.85.1(17:16798)
06:58:39: RSVP 129.44.85.1_16798-129.44.85.5_16502: remove sender host PATH
129.44.85.5(16502) <- 129.44.85.1(17:16798)
06:58:39: RSVP session 129.44.85.5_16502: send path teardown multicast about
129.44.85.5 on Ethernet0/0
06:58:39: RSVP session 129.44.85.5_0: IP to 129.44.85.5 length=164
checksum=A6E8 TOS=0x00 (Ethernet0/0)
06:58:39: RSVP 129.44.85.5_16502-129.44.85.1_16798: remove receiver host
RESV 129.44.85.1(16798) <- 129.44.85.5(17:16502)
06:58:39: RSVP 129.44.85.5_16502-129.44.85.1_16798: remove Ethernet0/0 RESV
request 129.44.85.1(16798) <- 129.44.85.5(17:16502)
06:58:39: RSVP session 129.44.85.1_16798: send reservation teardown to
129.44.85.5 about 129.44.85.1
06:58:39: RSVP session 129.44.85.1_0: IP to 129.44.85.5 length=88
checksum=6448 TOS=0x00 (Ethernet0/0)
06:58:39: RSVP 129.44.85.5_4101-129.44.85.1_42724: message received from
129.44.85.5, TOS 0x0
06:58:39: RSVP 129.44.85.5_16502-129.44.85.1_16798: PATH TEAR message for
129.44.85.1 (Ethernet0/0) from 129.44.85.5
06:58:39: RSVP 129.44.85.5_16502-129.44.85.1_16798: remove Ethernet0/0 PATH
129.44.85.1(16798) <- 129.44.85.5(17:16502)
06:58:39: RSVP 129.44.85.5_4102-129.44.85.1_25668: message received from
129.44.85.5, TOS 0x0
06:58:39: RSVP 129.44.85.1_16798-129.44.85.5_16502: RESV TEAR message for
129.44.85.5 (Ethernet0/0) from 129.44.85.5
4.85.5_17340: remove receiver host RESV 129.44.85.5(17340) <-
129.44.85.1(17:16780)
06:57:23: RSVP 129.44.85.1_16780-129.44.85.5_17340: remove Ethernet0/0 RESV
request 129.44.85.5(17340) <- 129.44.85.1(17:16780)
06:57:23: RSVP session 129.44.85.5_17340: send reservation teardown to
129.44.85.1 about 129.44.85.5
06:57:23: RSVP: version:1 flags:0000 type:RTEAR cksum:6110 ttl:255
reserved:0 length:88
06:57:23: SESSION type 1 length 12:
06:57:23: Destination 129.44.85.5, Protocol_Id 17, Don't Police ,
DstPort 17340
06:57:23: HOP type 1 length 12: 812C5505
06:57:23: : 00000000
06:57:23: STYLE type 1 length 8 :
06:57:23: RSVP_FF_OPTION
06:57:23: FLOWSPEC type 2 length 36:
06:57:23: version = 0 length in words = 7
06:57:23: service id = 5, service length = 6
06:57:23: tspec parameter id = 127, tspec flags = 0, tspec length = 5
06:57:23: average rate = 3000 bytes/sec, burst depth = 120 bytes
06:57:23: peak rate = 3000 bytes/sec
06:57:23: min unit = 0 bytes, max unit = 1500 bytes
06:57:23: FILTER_SPEC type 1 length 12:
06:57:23: Source 129.44.85.1, udp_source_port 16780
06:57:23:
06:57:23: RSVP: version:1 flags:0000 type:PTEAR cksum:0000 ttl:255
reserved:0 length:164
06:57:23: SESSION type 1 length 12:
06:57:23: Destination 129.44.85.5, Protocol_Id 17, Don't Police ,
DstPort 17340
06:57:23: HOP type 1 length 12: 812C5501
06:57:23: : 00000000
06:57:23: SENDER_TEMPLATE type 1 length 12:
06:57:23: Source 129.44.85.1, udp_source_port 16780
06:57:23: SENDER_TSPEC type 2 length 36:
06:57:23: version=0, length in words=7
06:57:23: Token bucket fragment (service_id=1, length=6 words
06:57:23: parameter id=127, flags=0, parameter length=5
06:57:23: average rate=3000 bytes/sec, burst depth=120 bytes
06:57:23: peak rate =3000 bytes/sec
06:57:23: min unit=0 bytes, max unit=0 bytes
06:57:23: ADSPEC type 2 length 84:
06:57:23: version=0 length in words=19
06:57:23: General Parameters break bit=0 service length=8
06:57:23: IS Hops:0
06:57:23: Minimum Path Bandwidth (bytes/sec):2147483647
06:57:23: Path Latency (microseconds):0
06:57:23: Path MTU:-1
06:57:23: Guaranteed Service break bit=0 service length=8
06:57:23: Path Delay (microseconds):0
06:57:23: Path Jitter (microseconds):0
06:57:23: Path delay since shaping (microseconds):0
06:57:23: Path Jitter since shaping (microseconds):0
06:57:23: Controlled Load Service break bit=0 service length=0
06:57:23:
06:57:23: RSVP 129.44.85.1_16780-129.44.85.5_17340: PATH TEAR message for
129.44.85.5 (Ethernet0/0) from 129.44.85.1
06:57:23: RSVP 129.44.85.1_16780-129.44.85.5_17340: remove Ethernet0/0 PATH
129.44.85.5(17340) <- 129.44.85.1(17:16780)
06:57:23: RSVP: version:1 flags:0000 type:RTEAR cksum:0000 ttl:255
reserved:0 length:88
06:57:23: SESSION type 1 length 12:
06:57:23: Destination 129.44.85.1, Protocol_Id 17, Don't Police ,
DstPort 16780
06:57:23: HOP type 1 length 12: 812C5501
06:57:23: : 00000000
06:57:23: STYLE type 1 length 8 :
06:57:23: RSVP_FF_OPTION
06:57:23: FLOWSPEC type 2 length 36:
06:57:23: version = 0 length in words = 7
06:57:23: service id = 5, service length = 6
06:57:23: tspec parameter id = 127, tspec flags = 0, tspec length = 5
06:57:23: average rate = 3000 bytes/sec, burst depth = 120 bytes
06:57:23: peak rate = 3000 bytes/sec
06:57:23: min unit = 0 bytes, max unit = 1500 bytes
06:57:23: FILTER_SPEC type 1 length 12:
06:57:23: Source 129.44.85.5, udp_source_port 17340
06:57:23:
06:57:23: RSVP 129.44.85.5_17340-129.44.85.1_16780: RESV TEAR message for
129.44.85.1 (Ethernet0/0) from 129.44.85.1
----- Original Message -----
From: "William Chen" <kwchen@netvigator.com>
To: "Richard Dumoulin" <richard.dumoulin@vanco.es>; "Sergio Jimenez
Arguedas" <sejimenez@its.co.cr>; <ccielab@groupstudy.com>
Sent: Friday, May 21, 2004 8:30 PM
Subject: Re: RSVP FOR VOICE TRAFFIC!!
> Hi,
>
> The problem you have is that the two VOIP dial-peers don't associated
> with each other.
>
> You need command "incoming called-number xxx" in the dial-peer
> configuration:
>
> > R1_Config
> >
> > dial-peer voice 3 voip
> > destination-pattern 5000
> incoming called-number 5302
> > session target ipv4:129.44.85.5
> > req-qos guaranteed-delay
> > acc-qos guaranteed-delay
> >
> >
> > R2_Config
> >
> > dial-peer voice 3 voip
> > destination-pattern 5302
> incoming called-number 5000
> > session target ipv4:129.44.85.1
> > req-qos guaranteed-delay
> > acc-qos guaranteed-delay
>
> Best Regards,
> William Chen
>
> ----- Original Message -----
> From: "Richard Dumoulin" <richard.dumoulin@vanco.es>
> To: "Sergio Jimenez Arguedas" <sejimenez@its.co.cr>;
> <ccielab@groupstudy.com>
> Sent: Saturday, May 22, 2004 9:19 AM
> Subject: RE: RSVP FOR VOICE TRAFFIC!!
>
>
> > I'll give it a try. The default codec is G729ar8 which needs something
> like
> > 30 Kbps aprox without CRTP. So maybe your 24Kbps reservation with RSVP
is
> > not enough ?
> > Can you try "ip rsvp bandwidth 40 40" or "req-qos controlled-load"
instead
> ?
> >
> > "debug ip rsvp" might be useful,
> >
> > --Richard
> >
> > -----Original Message-----
> > From: Sergio Jimenez Arguedas [mailto:sejimenez@its.co.cr]
> > Sent: sabado, 22 de mayo de 2004 3:10
> > To: ccielab@groupstudy.com
> > Subject: RSVP FOR VOICE TRAFFIC!!
> >
> >
> > Hi Group!!!
> >
> >
> > I have a problem with a VoIP Scenario using RSVP:
> >
> >
> >
> >
>
TEL-----------R1-e0/0-----------------------------------e0/0-R2-------------
> > -
> > --TEL
> >
> >
> >
> > R1_Config
> >
> > interface Ethernet0/0
> > ip address 129.44.85.1 255.255.255.0
> > half-duplex
> > fair-queue 64 256 1
> > ip rsvp bandwidth 24 24
> > !
> > dial-peer voice 2 pots
> > destination-pattern 5302
> > port 3/0/1
> > !
> > dial-peer voice 3 voip
> > destination-pattern 5000
> > session target ipv4:129.44.85.5
> > req-qos guaranteed-delay
> > acc-qos guaranteed-delay
> >
> >
> > R2_Config
> >
> > interface Ethernet0/0
> > ip address 129.44.85.5 255.255.255.0
> > half-duplex
> > fair-queue 64 256 1
> > ip rsvp bandwidth 24 24
> > !
> > dial-peer voice 1 pots
> > destination-pattern 5000
> > port 1/0/0
> > !
> > dial-peer voice 3 voip
> > destination-pattern 5302
> > session target ipv4:129.44.85.1
> > req-qos guaranteed-delay
> > acc-qos guaranteed-delay
> >
> > Without the RSVP config, I don4t have problems!!!
> >
> > But, with RSVP I got it:
> >
> > R2#csim start 5302
> > csim: called number = 5302, loop count = 1 ping count = 0
> >
> > csim err csimDisconnected recvd DISC cid(55)
> > csim: loop = 1, failed = 1
> > csim: call attempted = 1, setup failed = 1, tone failed = 0
> >
> >
> > Can somebody help me, please?
> >
> >
> > Just tell me if you some show or debug cmd!!!
> >
> >
> > Rgds,
> >
> >
> > Sergio
> >
> > _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> > _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:15 GMT-3