Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

SRST - Why does call forward require a #

Have a situation when router falls into SRST, all calls are working fine, but we notice that Call Forward will time out if you don't include a # at the end of the dial string.

By the way, we're talking call forward initiated at the phone, not configuration in IOS.

Meanwhile, if the phone dials the same number no # is required, which makes me think it's not a dial-peer problem, or at least not a problem with matching a destination pattern.

Does anyone know what might be causing this or know of a solution so that # does not have to be entered. Apart from manually configuring call forward in the router.

Thanks in advance.

6 REPLIES

Re: SRST - Why does call forward require a #

Well it is definatly a dial-peer issue. There is a call-forward pattern under the srst config, maybe that pattern is targeting things with a # at the end specifically. Something like .T# if it is, just change it to .T ;) . Also paste the running config!

HTH, please rate useful posts.

Chad

New Member

Re: SRST - Why does call forward require a #

Okay... what follows is what I consider possibly relevant portions of the config.

IP's have been excluded, and any real phone number changed to some version of 111222XXXX.

I notice under fallback "transfer-pattern .T blind". Chad mentioned changing .T, but what does the blind component do?

Secondly, I see a second pattern of 10 dots. I suspect this is the real culprit. Anything less than 10 digits is likely getting an interdigit timeout because of this.

Thoughts?

___________________________________________

ccm-manager fallback-mgcp

ccm-manager redundant-host

ccm-manager mgcp

ccm-manager music-on-hold

ccm-manager config server

ccm-manager config

!

mgcp

mgcp call-agent service-type mgcp version 0.1

mgcp rtp unreachable timeout 1000 action notify

mgcp modem passthrough voip mode nse

mgcp ip qos dscp cs3 signaling

mgcp package-capability rtp-package

mgcp package-capability sst-package

mgcp package-capability pre-package

no mgcp package-capability res-package

no mgcp package-capability fxr-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp rtp payload-type g726r16 static

mgcp bind control source-interface Loopback2

mgcp bind media source-interface Loopback2

!

mgcp profile default

!

sccp local Loopback2

sccp ccm identifier 1 priority 1 version 5.0.1

sccp ccm identifier 2 priority 2 version 5.0.1

sccp

!

sccp ccm group 999

description conferencing

bind interface Loopback2

associate ccm 1 priority 1

associate ccm 2 priority 2

associate profile 999 register

!

dspfarm profile 999 conference

description conference profile 999

codec g711ulaw

codec g729r8

maximum sessions 4

associate application SCCP

!

dial-peer voice 99999 pots

description default inbound dial peer

incoming called-number .

direct-inward-dial

!

dial-peer voice 1001 pots

description Service PRI Primary

preference 1

destination-pattern [34679]11

clid network-number 1112223333

port 0/3/0:23

forward-digits 3

!

dial-peer voice 2001 pots

description Primary 10 Digit PSTN calls

preference 1

destination-pattern [2-9]..[2-9]......

port 0/3/0:23

forward-digits 10

!

dial-peer voice 3001 pots

description Primary LD calls

preference 1

destination-pattern 1[2-9]..[2-9]......

port 0/3/0:23

forward-digits 11

!

dial-peer voice 4001 pots

description Primary International calls

preference 1

destination-pattern 011T

port 0/3/0:23

forward-digits all

!

dial-peer voice 5001 pots

description Block 900 calls

destination-pattern 1900[2-9]......

!

dial-peer voice 6001 pots

description Block 976 Calls

destination-pattern 1976[2-9]......

!

dial-peer voice 7001 pots

description Block 600 Calls

destination-pattern 1600[2-9]......

!

gateway

timer receive-rtp 600

!

call-manager-fallback

max-conferences 6 gain -6

transfer-system full-consult

limit-dn 7910 2

limit-dn 7940 2

limit-dn 7960 2

limit-dn 7970 2

ip source-address port 2000

max-ephones 36

max-dn 72 dual-line

transfer-pattern .T blind

transfer-pattern ..........

voicemail 1112224444

call-forward pattern ..........

call-forward busy 1112225555

call-forward noan 1112225555 timeout 20

!

ephone-hunt 1 sequential

pilot 1112226666

final 1112227777

present-call onhook-phone

!

Re: SRST - Why does call forward require a #

looking at this I still say it should be call-forward pattern .T but I don't see how this would fix your problem :)..

Chad

New Member

Re: SRST - Why does call forward require a #

I think there is a call forward pattern command you need to add specifically to each ephone. just like the one you have in call-manager-fallback.

New Member

Re: SRST - Why does call forward require a #

Oh man, I hope that's not the case. I have an attempt to fix in place. If testing still has the problem, then I'll try this.

New Member

Re: SRST - Why does call forward require a #

Yeah, that's I'm trying now. I made the following changes yesterday before reading this.

Call-manager-fallback

no transfer pattern ..........

no call-forward pattern ..........

call-forward pattern .T

I'm having the end users test call forwarding to internal numbers and external numbers (internal just happen to have a 10 digit dialplan (yuck)), so I should know soon whether or not they still need a # to complete the string.

215
Views
0
Helpful
6
Replies