09-10-2013 10:30 AM - edited 03-16-2019 07:17 PM
I configured CorpHQ, Branch1, & Branch2 with identical RSVP & MTP configurations in both the gateway & CUCM, however, when I attempt to make calls to/from Branch2, I get a NOT ENOUGH BANDWIDTH error. Calls beweeen CorpHQ & Branch1 work fine. On the CUCM, I configured REGIONS, DEVICE POOLS, LOCATIONS, SRST REFERENCES,MTPs, MRGs, and MRGLs for all 3 locations. Below is the configuration for all 3 gateways.
Thanks,
BRANCH2#
interface Serial0/1/0.1 point-to-point
description == FR To HQ
ip address 177.0.201.2 255.255.255.0
ip pim dense-mode
snmp trap link-status
frame-relay interface-dlci 102
ip rsvp bandwidth 136
!
sccp local Loopback0
sccp ccm 177.1.254.3 identifier 3 priority 3 version 5.0.1
sccp ccm 177.1.10.10 identifier 1 priority 1 version 5.0.1
sccp ccm 177.1.10.20 identifier 2 priority 2 version 5.0.1
sccp
!
sccp ccm group 1
bind interface Loopback0
associate ccm 2 priority 1
associate ccm 1 priority 2
associate ccm 3 priority 3
associate profile 1 register Br2-729-MTP
associate profile 2 register Br2-711-MTP
!
dspfarm profile 1 mtp
codec g729ar8
codec g729r8
rsvp
maximum sessions software 10
associate application SCCP
!
dspfarm profile 2 mtp
codec g711ulaw
rsvp
maximum sessions software 10
associate application SCCP
Solved! Go to Solution.
09-10-2013 12:11 PM
This can cause not enough BW message:
- BW exhausted
- Phones not associated with an RSVP agent (check MGRL)
- One segment in the path has insufficient BW for the call
- RSVP per flow needs 16 kbps extra for the initial reservation
- Connectivity issues with the agent
Just go over this list one by one and tell us what you find out.
Please rate helpful answers!
09-10-2013 11:32 AM
Hi Ron.
How much bandwidth did you allocate in locations between DPs?
Regards
Carlo
Sent from Cisco Technical Support iPhone App
09-10-2013 11:51 AM
Carlo:
Bandwidth for Audio & Video is UNLIMITED...
Thanks,
Ron
09-10-2013 12:11 PM
This can cause not enough BW message:
- BW exhausted
- Phones not associated with an RSVP agent (check MGRL)
- One segment in the path has insufficient BW for the call
- RSVP per flow needs 16 kbps extra for the initial reservation
- Connectivity issues with the agent
Just go over this list one by one and tell us what you find out.
Please rate helpful answers!
09-10-2013 02:03 PM
Amine:
The MTPs are registered. ip rsvp bandwidth 136 is enough bandwidth to make 5 calls. There is no issue with the MRGL config.
I cannot decipher the debug output from the CALLING phone.
CALLING PHONE
Branch1#
RSVP-RESV: Admitting new reservation: 481BAF2C
RSVP-RESV: reservation was installed: 481BAF2C
RSVP: 177.1.254.2_17690->177.1.254.1_17978[0.0.0.0]: Expiring sender host PATH state, reason: Local application requested tear
RSVP: 177.1.254.2_17690->177.1.254.1_17978[0.0.0.0]: building hop object with src addr: 177.0.101.2
RSVP: 177.1.254.2_17690->177.1.254.1_17978[0.0.0.0]: Sending PathTear message to 177.1.254.1
RSVP: 177.1.254.2_17690->177.1.254.1_17978[0.0.0.0]: Expiring Serial0/1/0.1 RESV state, reason: Local application requested tear
RSVP: 177.1.254.2_17690->177.1.254.1_17978[0.0.0.0]: Expiring Serial0/1/0.1 RESV state, reason: Local application requested tear (17:17690)
RSVP: 177.1.254.1_17978->177.1.254.2_17690[0.0.0.0]: Expiring RESV state, reason: Local application requested tear
RSVP: 177.1.254.1_17978->177.1.254.2_17690[0.0.0.0]: Expiring receiver host RESV state, reason: Local application requested tear (17:17978)
RSVP: 177.1.254.1_17978->177.1.254.2_17690[0.0.0.0]: Expiring Serial0/1/0.1 RESV request state, reason: Local application requested tear
RSVP: 177.1.254.1_17978->177.1.254.2_17690[0.0.0.0]: Sending ResvTear message to 177.0.101.1
RSVP-MSG: 177.1.254.1_17978->177.1.254.2_17690[0.0.0.0]: Received PathTear message from 177.1.254.1 (on Serial0/1/0.1)
RSVP: 177.1.254.1_17978->177.1.254.2_17690[0.0.0.0]: Expiring Serial0/1/0.1 PATH state, reason: PathTear arrival
RSVP-MSG: 177.1.254.2_17690->177.1.254.1_17978[0.0.0.0]: Received ResvTear message from 177.0.101.1 (on Serial0/1/0.1)
RSVP-MSG: 177.1.254.2_17690->177.1.254.1_17978[0.0.0.0]: Dropping ResvTear with unrecognized LIH in HOP (may be due to a state which was already deleted)
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: Received Path message from 127.0.0.1 (on sender host)
RSVP: new path message passed parsing, continue...
RSVP: Triggering outgoing Path due to incoming Path change or new Path
RSVP: Triggering outgoing Path refresh
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: Path refresh, Event: rmsg not enabled or ack rcvd, State: trigger to normal
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: Path refresh (msec), config: 30000 curr: 30000 xmit: 30000
RSVP: Triggering outgoing Path due to incoming Path change or new Path
RSVP: Triggering outgoing Path refresh
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: Path refresh, Event: rmsg not enabled or ack rcvd, State: trigger to normal
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: Path refresh (msec), config: 30000 curr: 30000 xmit: 30000
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: Sending Path message to 177.1.254.3
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: building hop object with src addr: 177.0.101.2
RSVP: session 177.1.254.2_19552[0.0.0.0]: Received Resv message from 127.0.0.1 (on receiver host)
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Successfully parsed Resv message from 127.0.0.1 (on receiver host)
RSVP-MSG: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: no matching path state for Resv
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Received Path message from 177.0.201.2 (on Serial0/1/0.1)
RSVP: new path message passed parsing, continue...
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: PATH: non-RSVP-capable hop between prev-hop and me (ip ttl=253, rsvp ttl=254) for new path
RSVP: session 177.1.254.2_19552[0.0.0.0]: Received Resv message from 127.0.0.1 (on receiver host)
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Successfully parsed Resv message from 127.0.0.1 (on receiver host)
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: reservation not found--new one
RSVP-RESV: Admitting new reservation: 48174808
RSVP-RESV: Locally created reservation. No admission/traffic control needed
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: start requesting 40 kbps FF reservation on Serial0/1/0.1, neighbor 177.0.201.2
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: start requesting 40 kbps FF reservation on Serial0/1/0.1, neighbor 177.0.201.2
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Refresh RESV, req=4815EE80 [cleanup timer is not awake]
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Resv refresh, Event: rmsg not enabled or ack rcvd, State: trigger to normal
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Resv refresh (msec), config: 30000 curr: 30000 xmit: 30000
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Sending Resv message to 177.0.201.2
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: building hop object with src addr: 177.0.101.2
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: Expiring sender host PATH state, reason: Local application requested tear
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: building hop object with src addr: 177.0.101.2
RSVP: 177.1.254.2_19552->177.1.254.3_19474[0.0.0.0]: Sending PathTear message to 177.1.254.3
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Expiring RESV state, reason: Local application requested tear
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Expiring receiver host RESV state, reason: Local application requested tear (17:19474)
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Expiring Serial0/1/0.1 RESV request state, reason: Local application requested tear
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Sending ResvTear message to 177.0.201.2
RSVP-MSG: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Received PathTear message from 177.1.254.3 (on Serial0/1/0.1)
RSVP: 177.1.254.3_19474->177.1.254.2_19552[0.0.0.0]: Expiring Serial0/1/0.1 PATH state, reason: PathTear arrivalBranch1#
CALLED PHONE
Branch2#
RSVP: session 177.1.254.3_19132[0.0.0.0]: Received Resv message from 127.0.0.1 (on receiver host)
RSVP: 177.1.254.2_17938->177.1.254.3_19132[0.0.0.0]: Successfully parsed Resv message from 127.0.0.1 (on receiver host)
RSVP-MSG: 177.1.254.2_17938->177.1.254.3_19132[0.0.0.0]: no matching path state for Resv
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Received Path message from 127.0.0.1 (on sender host)
RSVP: new path message passed parsing, continue...
RSVP: Triggering outgoing Path due to incoming Path change or new Path
RSVP: Triggering outgoing Path refresh
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Path refresh, Event: rmsg not enabled or ack rcvd, State: trigger to normal
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Path refresh (msec), config: 30000 curr: 30000 xmit: 30000
RSVP: Triggering outgoing Path due to incoming Path change or new Path
RSVP: Triggering outgoing Path refresh
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Path refresh, Event: rmsg not enabled or ack rcvd, State: trigger to normal
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Path refresh (msec), config: 30000 curr: 30000 xmit: 30000
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Sending Path message to 177.1.254.2
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: building hop object with src addr: 177.0.201.2
RSVP: session 177.1.254.2_17938[0.0.0.0]: Received Resv message from 177.0.101.2 (on Serial0/1/0.1)
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Successfully parsed Resv message from 177.0.101.2 (on Serial0/1/0.1)
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: reservation not found--new one
RSVP-RESV: Admitting new reservation: 4791EFB0
RSVP-RESV: reservation was installed: 4791EFB0
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Expiring sender host PATH state, reason: Local application requested tear
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: building hop object with src addr: 177.0.201.2
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Sending PathTear message to 177.1.254.2
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Expiring Serial0/1/0.1 RESV state, reason: Local application requested tear
RSVP: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Expiring Serial0/1/0.1 RESV state, reason: Local application requested tear (17:19132)
RSVP-MSG: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Received ResvTear message from 177.0.101.2 (on Serial0/1/0.1)
RSVP-MSG: 177.1.254.3_19132->177.1.254.2_17938[0.0.0.0]: Dropping ResvTear with unrecognized LIH in HOP (may be due to a state which was already deleted)
09-10-2013 02:15 PM
Amine:
The issue was a typo in the ip rsvp bandwidth statement.
Thanks for your assistance.
Ron
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide