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

FXO On MGCP controlled VIC does not ring through during SRST Fallback

I have SRST running on a 2600 router (12.2(8)T) . The FXO ports are under MGCP control to a CallManager (3.2). In SRST fallback, I expected all calls to go to a single, default destination number. Instead the FXO answers and no phone is connected. Does fallback use the station ID defined on the port instead .. in that case I would need to have the station ID match the desired phone DN?

call-manager-fallback:

ip source-address (not shown here....)

max-ephones 12

max-dn 12

huntstop

default-destination 47508

voicemail (not shown here....)

time-format 12

date-format mm-dd-yy

transfer-pattern .....

keepalive 30

interdigit timeout 10

Limit number of DNs per phone:

7910: 6

7935: 6

7940: 6

7960: 6

ephone-dn 4

name 47508

huntstop

!

voice-port 50/0/4

station-id name 47508

Voice Port:

!

voice-port 1/1/0

station-id number 8001235508

!

7 REPLIES
New Member

Re: FXO On MGCP controlled VIC does not ring through during SRST

SRST use h323. Configure a connection plar in your voice-port to the dn of the phone you want to ring.

New Member

Re: FXO On MGCP controlled VIC does not ring through during SRST

According to the reference below, connection plar shouldn't be used on a voice port when configured for MGCP. It goes on to say "However, H.323 and MGCP configuration will coexist when you enable MGCP gateway fallback or Survivable Remote Site Telephony (SRST)." If I configure plar, will MGCP take precedence?

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_access/config/mgcpcm30.htm

New Member

Re: FXO On MGCP controlled VIC does not ring through during SRST

I beleive that to be the case, but personally I would suggest going h323 only and not use MGCP at all if possible.

Cisco Employee

Re: FXO On MGCP controlled VIC does not ring through during SRST

The only code that support mgcp fallback to h.323 at this time is 12.2(2)xn and it does not support SRST. So you will have to wait for a version of code that has both of these features in it. I have heard it is coming just don't know the exact release.

Thank you,

-Mckee

New Member

Re: FXO On MGCP controlled VIC does not ring through during SRST

I understood going into this configuration that mgcp fallback to h.323 with SRST wasn't released yet, so I kept the config simple for now. My issue is that the default-destination (47508) is not ringing in fallback. It bothers me that the fallback dialpeers don't show an ephone of the name/number. I know for a fact that 47508 is capable of making/receiving calls during fallback to other phones on the same router. I don't need fallback to h.323 if the default-destination command was working correctly - does the ephone list needs a forced update to get the names field correct so the incoming call can be matched? Here's a partial show call-manager-fallback:

ip source-address (not shown here...)

max-ephones 12

max-dn 12

huntstop

access-code fxo 9

default-destination 47508

transfer-pattern .....

keepalive 30

interdigit timeout 10

Limit number of DNs per phone:

7910: 6

7935: 6

7940: 6

7960: 6

ephone-dn 1

name 47502

huntstop

ephone-dn 2

name 47501

huntstop

ephone-dn 3

name 47503

huntstop

ephone-dn 4

huntstop

ephone-dn 5

huntstop

.

.

ephone-dn 12

huntstop

voice-port 50/0/1

station-id name 47502

!

voice-port 50/0/2

station-id name 47501

!

voice-port 50/0/3

station-id name 47503

!

voice-port 50/0/4

!

voice-port 50/0/5

.

.

New Member

Re: FXO On MGCP controlled VIC does not ring through during SRST

I believe that I am having the same type of problem. From everything I've read, I am pretty sure that it should work, but on inbound calls I get a ring then fast busy.

I am probably missing something basic, but cannot figure out what it is.

Any help would be greatly appreciated.

heather

2620Hancock#sh call-manager-fallback

CONFIG

======

ip source-address 192.168.15.1 port 2000

max-ephones 24

max-dn 96

huntstop

dialplan-pattern 2 617XXX82.. extension-length 4

default-destination 8200

moh music-on-hold.au

time-format 24

date-format mm-dd-yy

transfer-pattern 82..

alias 1 82.. to 8229

keepalive 30

interdigit timeout 10

Limit number of DNs per phone:

7910: 1

7935: 6

7940: 6

7960: 6

2620Hancock#sh call-manager-fallback ephone-dn

ephone-dn 1

number 8211

name 8211

huntstop

ephone-dn 2

number 8200

name 8200

huntstop

2620Hancock#sh call-manager-fallback voice-port

voice-port 50/0/1

station-id number 617XXX8211

station-id name 8211

!

voice-port 50/0/2

station-id number 6176XXX8200

station-id name 8200

!

New Member

Re: FXO On MGCP controlled VIC does not ring through during SRST

I'd like to see this work, so I opened a TAC ticket on default-destination not working correctly. TAC claims this to be an unsupported config since SRST is an H.323 service and this version software is supports H.323 and MGCP on a mutually exclusive basis (first release will be 12.2.11). I thought that the default-destination command should work just like you did. In my case I get a single ring, answer, and a silent trunk - no busy. Does the other direction work - can users dial out during SRST fallback with your config?

Regards,

Earle

318
Views
0
Helpful
7
Replies
CreatePlease to create content