A student's open lab: learning and sharing, free for everyone.

SIP UniverseFree University

Home / Cisco CUBE, CUCM, and Unity Connection / Dial peers select the SIP next hop

Dial peers select the SIP next hop

dial-peer voice N voip, session protocol sipv2, and session target ipv4: name a SIP next hop.

Learn in 5 minutes

  1. Read the three documented dial-peer lines
  2. Point session target at the intended peer
  3. Keep extra IOS commands out of this lesson

Visual

session target becomes the Request-URI host · study drawing · cyphermonkeylabs.com CUCMCUBECarrier INVITE 100 INVITE 100

SVG HTML PNG

Matching keys beyond these lines are in the configuration guide for your release.

Worked example

Read dial peer 200 This is the carrier dial peer. Where will CUBE send the outbound INVITE?

  1. Read session protocol.
  2. Read session target.
  3. Name the address.

Vendor menus, ports, and license names change. Confirm before relying on a sentence that is not an RFC.

Fault

Outbound INVITEs leave CUBE toward 203.0.113.10 and the carrier never sees the call.

ipv4:203.0.113.10 is Alice, not 192.0.2.40.

Quiz

session protocol sipv2 selects


session target ipv4:192.0.2.40 sends the call to


dial-peer voice 200 voip creates


The phone address in this lab is


CUCM’s lab address is


Extra matching commands belong


Ecosystem

Glossary, sister systems, and the integration seam for this room.

Quality management and recording QM scores interactions. The standardized way an SBC forks a session to a recorder is SIPREC.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper