cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
495
Views
0
Helpful
2
Replies

SRST - FXO outbound calling not working

Jon Nelson
Level 3
Level 3

I'm running SRST on a Cisco 2811 12.3(11)T5. When I disconnect the WAN link to test incoming and outgoing calling, I am able to get incoming calls, but I am unable to make outgoing calls. When I dial, the router only accepts 3 digits and then attempts to dial and of course fails. We are not using MGCP with this Call Manager implementation

Here is the relevant config information:

voice-port 0/2/0

timeouts interdigit 3

connection plar 406

caller-id enable

dial-peer voice 90 pots

destination-pattern 9T

incoming called-number .

port 0/2/0

!

dial-peer voice 100 voip

destination-pattern ...

voice-class codec 1

session target ipv4:172.16.0.20

incoming called-number .

dtmf-relay h245-alphanumeric

no vad

call-manager-fallback

secondary-dialtone 9

max-conferences 4

ip source-address 172.16.1.1 port 2000

max-ephones 12

max-dn 12 dual-line

system message primary SRST Active

alias 1 6000 to 400 preference 2

Any help would be great!

2 Replies 2

Erick Bergquist
Level 6
Level 6

This dialpeer has a match for 3 digit number so this is why 3 digits then busy.

Since your inbound connection plar goes to 406 you can change this to destination-pattern 4.. to get by this. However if you are getting other numbers on other ports you may have to add more dial-peers, or change your destination pattern, or add a translation rule to better handle the numbers.

dial-peer voice 100 voip

destination-pattern ...

voice-class codec 1

session target ipv4:172.16.0.20

incoming called-number .

dtmf-relay h245-alphanumeric

no vad

ebergquist,

Thanks for the reply. I should have included the debug statements to show that the outgoing calls are matching dial-peer 90 and not the dial-peer voice 100. I am almost wondering if I need to have a better destination pattern than 9T for the local calling.

Thank you,

Jon