Home › Spotlights
Cisco routers — branch and edge sourcing
Branch and edge routing sits naturally beside the Cisco switching lines on this desk — routers, modules and the switches behind them on one BOM.
Routers with their modules
A Cisco router inquiry should travel with its module list: interface cards, and PVDM4 DSP modules where the branch runs voice. The PVDM4-64 is one of our listed products, which is why voice-enabled branch builds are a named pattern here.
State the WAN mix per site — Ethernet, serial, cellular backup — and whether sites repeat. Repeated site designs price faster and consolidate better.
Cisco router inquiry checklist
- Router models or the branch role and throughput
- Interface and module list per router
- Voice channels where PVDM DSP is involved
- Site count and whether the design repeats
From branch list to router shortlist
Router inquiries work best as branch briefs: what each site connects to, what terminates on the router, and what rides through it. A headquarters edge, a mid-size branch and a small office running the same routing family still price as three different builds, because the interface mix is what the money follows.
Where a project has already chosen its models, send the strings and they are priced exactly. Where the choice is still open, send the branch facts — circuit types, interface counts, voice channels — and the quotation proposes model lines, clearly marked as proposals, sized from the facts you gave.
Voice modules belong on the same list
The classic short order is a router without its voice resources — DSP modules are separate lines, sized by channel count, and a gateway that arrives without them is a router that cannot do the job it was bought for. If the branch design carries voice, put the channel counts on the inquiry — per site if they vary — and the module lines join the quotation in the right size.
The same discipline applies to interface cards and memory or software choices the string leaves open. Each open element is named on the quotation with the choice that was priced, so nothing about the build is settled by assumption.
Rollouts price as kits
A thirty-branch rollout is not thirty router purchases. It is one pattern bought thirty times — and the pattern deserves a kit: the router build, its modules, its rack and console accessories, and a spare ratio the project sets. Priced as a kit, the rollout keeps every branch identical and turns branch thirty into a repetition instead of a new negotiation.
Exceptions are priced as exceptions. Sites with different circuits or voice loads are broken out of the pattern and priced on their own facts, listed separately so the pattern's price stays clean and the exceptions stay visible.
Common questions
Can routers and switches for one site ship together?
Yes — site kits consolidate into single shipments.
Do you quote PVDM4 modules separately?
Yes — see the dedicated PVDM4 sourcing page, or add them to the router BOM.
What does a router inquiry need?
Per-site facts: WAN services, interface counts, voice channel counts where applicable, and destination. Model strings if chosen; branch facts if not.
What if one branch differs from the rollout pattern?
Mark it on the list. It is priced on its own facts as a separate line group, while the rest of the rollout keeps the pattern price.