03-25-2020 11:07 AM
Hello, I have a cisco 2921 router and I would like to know how to enable port 5060 so that my ITSP can send information so I can perform outbound/inbound calls.
03-25-2020 11:19 AM - edited 03-25-2020 11:19 AM
If you don't have any access list applied to an interface all you need to do is properly configure the voice session voip and cube commands to enable it. Note the trust list below would be to be the source of the traffic.
What is your true topology look like that might help with a better answer.
voice service voip
allow-connections sip to sip
ip address trusted list ipv4 <ipv4-address> [<ipv4 network-mask>]
Who is your ITSP? If any of the major players you can find sample configuration here.
SIP dial peers on the router are UDP by default I believe you can change them to TCP if you want.
03-25-2020 11:28 AM
In addition to great response (+5), port 5060 is the default SIP port and you don't need to change anything on Cisco IOS device when pointing to a SIP destination unless you are using different port or if you need to use TCP instead of UDP in which case you would change session transport setting either globally or at a dial-peer level.
03-27-2020 06:24 PM
How would I do that? I'm showing that udp port 5060 is opened, when I do scans? is there a firewall acl that needs to be in place? or a dial-peer list? how can I tell since I cannot call outbound or recieve inbound? I really can't do a wireshark trace because everything is just extension to extension?
03-25-2020 11:29 AM
03-30-2020 11:33 AM
03-31-2020 08:09 AM
I think we need to see a schematic, or at least a description of the path from your CUBE to the ITSP. If you connect to the ITSP over the Internet it would be unusual (and worrying) to have a CUBE directly connected to the Internet without any sort of firewall configuration in place.
04-01-2020 03:41 AM
My dial peer setup:
When I do a debug ccsip messages and then term mon, the debug will not show messages.
Inbound Dial Peers:
dial-peer voice 101 voip
description Incoming LAN From CUCM
incoming called-number 9T
session protocol sipv2
codec g711ulaw
dtmf-relay rtp-nte
no vad
dial-peer voice 102 voip
description Outgoing LAN calls to CUCM
destination-pattern [2-9]
session protocol sipv2
session target ipv4:100.215.95.100
codec g711ulaw
dtmf-relay rtp-nte
no vad
Outgoing Dial Peers:
dial-peer voice 201 voip
description Incoming From ITSP To Router
incoming called-number [2-9]
session protocol sipv2
codec g711ulaw
dtmf-relay rtp-nte
no vad
dial-peer voice 202 voip
description Outgoing calls to ITSP
destination-pattern 9[2-9]
session protocol sipv2
session target ipv4:200.100.390.22
codec g711ulaw
dtmf-relay rtp-nte
no vad
04-01-2020 05:20 AM
I'm not sure I can get a sense of your numbering plan, and I suspect your dial peers are not correct. As written incoming numbers from ITSP are expected to be only one digit, and outbound calls two digits starting with 9. I think these need to be reviewed.
However what I was getting at was the actual network path between your gateway and the ITSP. How does it route to 200.100.390.22, and what other devices are in the path. Assuming it's permitted can you ping 200.100.390.22 from the CUBE?
04-01-2020 05:46 AM
If you don't get any output from the debug please check if you have no logging monitor set in our router. Also to check if the call is actually hitting the gateway at all you can do a debug voip dialpeer.
04-01-2020 03:34 PM
03-25-2020 11:41 AM
I can only dial from extension to extension, cannot call outbound or receive inbound. My ITSP tries to dial in using one of my DIDs and informs me that port 5060udp is not open.
I am also using CUCM 11.5?
03-25-2020 12:13 PM
Please post "debug ccsip messages"
03-30-2020 11:27 AM
03-30-2020 11:29 AM
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