Can't add dial-peers

[vanagon2tdi]

I have a 3745 with c3745-ipvoice-mz.123-11.T2.bin IOS.

Currently I am unable to add dial-peers, and I get this message:

calprigw1(config)#dial-peer voice 88363 pots

ERROR: could not add peer

If I reboot the router I will be able to add dial-peers.

Any ideas?

[dgahm]

If you have call manager fallback (SRST) configured you can reduce the max ephones and max dns which will free up space for more peers. Of course you will need to leave enough to cover the phones you have at that site.

[vanagon2tdi]

This router is not running CM, so there are no ephones registering.

I have the PRI modules installed (Conected to telco). Voice calls are sent to the various phones via dial-peers such as:

dial-peer voice 5556666 voip

huntstop

destination-pattern 2045556666

session target ipv4:10.111.0.2

dtmf-relay cisco-rtp

fax rate 7200

ip qos dscp cs5 media

no vad

Dave

[dgahm]

How many dial peers do you have?

show dial-peer voice summary

Can you use wild cards in your destination patterns?

destination-pattern 204555....

[vanagon2tdi]

I have aprox. 200 dial-peers. I have used wildcards were possible, but i will still have +200 dial-peers.

Dave

[carijit]

Can you please explain you you have 200+ dial-peers.

I hope you are not trying to create dial-peer for every phone in your cluster.

I dont balme the router if so.

But there are ways we can reduce the dial-peer numbers.

[carijit]

Can you please explain why you have 200+ dial-peers.

I hope you are not trying to create dial-peer for every phone in your cluster.

I dont balme the router if so.

But there are ways we can reduce the dial-peer numbers.

[vanagon2tdi]

We have 200+ dial-peers because we have no contiguous phone numbere sitting on different clent sites. Each site has a different LAN address. This makes it impossible to cluster them. We did have this same config working fine on a 2662 with as many or more dial peers.

[carijit]

If you can explain your topology that will be grat. I dont see any reason why you need 200+ dialpeers. If you have a Call Manager and if you define a dialpeer targeting to the Call Manager the Call Manager would take care of the call routing.

Also in this scenario MGCP would be be a more perfect candidate if you dont have any compeling reason to stick to H323