srst pri problem

[senolgokhan]

when srst enabled on the phones,calls go through analog lines but failed from e1 line. access code pri does not work.

12.4 ios

[Erick Bergquist]

Can you give more details?

Are inbound calls failing? If so, what do you hear? Do you have phones in fallback with the numbers coming in E1 PRI to receive the call?

You may need translation rules, alias command under fallback to get the numbers to work in fallback if CCM was manipulating the numbers, etc. Does your dial-peer for the PRI have direct-inward-dial on it?

Is this a MGCP or H323 gateway? If MGCP, is MGCP fallback configured correctly for the PRI to fallback and was it in H323 mode at time?

[senolgokhan]

hi,

part of the config is below.it's mgcp gateway.

dial-peer voice 9 pots

destination-pattern 9T

direct-inward-dial

port 0/2/0:15

!

!

call-manager-fallback

max-conferences 8 gain -6

ip source-address 172.16.0.3 port 2000

max-ephones 40

max-dn 50

access-code pri 9 direct-inward-dial

when i use access-code fxo everything is ok, i can call outside.

but when i use access-code pri , it doesnt work.(note:my pri line works when CCM works.)

IOS:c2800nm-ipvoicek9-mz.124-10.bin

thkns a lot

[Erick Bergquist]

Do inbound / outbound calls work fine without the access-code command? There is a cisco doc (don't have it offhand) that explains that a dial-peer of 9T and an access-code of 9 conflict with one another.

basically what the access-code 9 does is creates a virtual dial peer with 9 as destination pattern which doesn't work well with other dial-peers you created on your own with 9 in them.

You don't need the access-code command.

[senolgokhan]

hi

even when i remove acces-code still it doesnt work

dial-peer voice 9 pots

destination-pattern 9T

incoming called-number 3199...

direct-inward-dial

port 0/2/0:15

!

!

call-manager-fallback

max-conferences 8 gain -6

ip source-address 172.16.0.3 port 2000

max-ephones 40

max-dn 50

transfer-pattern 9T

[johncaston_2]

Hi,

If it works under CCM it indicates that your dial-peer is OK. I notice that you don't have any transfer pattern under call-manager-fallback. Here's a portion from one of my configs that works correctly (NB we use "1" to make an external call. The 9... is for internal extensions)

dial-peer voice 11 pots

tone ringback alert-no-PI

description Dial 1 outgoing

translation-profile outgoing OutBound

destination-pattern 1T

progress_ind alert enable 8

progress_ind progress enable 8

direct-inward-dial

port 0/0/0:15

call-manager-fallback

max-conferences 4 gain -6

ip source-address 192.168.106.1 port 2000

max-ephones 42

max-dn 42 dual-line

transfer-pattern 1T

transfer-pattern 9...

keepalive 10

default-destination 9100

call-forward noan 9100 timeout 12

Hope that helps

Cheers,

John

[senolgokhan]

hi again,

unfortunaltey it didnt work.Even if i add transfer-pattern ,still i can not call outside from E1 line. but i can call from fxo lines.

here is the last config :(

dial-peer voice 9 pots

destination-pattern 9T

incoming called-number 3199...

direct-inward-dial

port 0/2/0:15

!

!

call-manager-fallback

max-conferences 8 gain -6

ip source-address 172.16.0.3 port 2000

max-ephones 40

max-dn 50

transfer-pattern 9T

thnkx.

[johncaston_2]

Hi,

The only other thing I see is that you don't have an outgoing translation profile on your dialpeer to strip off the leading 9. I think that when you're calling from CCM, it's route plans do that.

You should have something like...

voice translation-rule 1

rule 1 /^9/ // type any unknown

voice translation-profile outBound

translate called 1

then in your dialpeer add....

translation-profile outgoing OutBound

Although I don't quite see why your FXO would work, unless it's going through a PBX that's stripping the leading 9 for you ????

Cheers,

John