Hi Erik,
I have the same problem as you described. The solution involves making the below changes under the gateway (in my case H.323 gateway) and asking the telco to let only numbers in my DID range to appear as calling party (they call it number validation or something like that).



hope this helps,

Abebe

Sorry I forgot to include the attachment

maybe configure phone1 with mobility and configured phone2's DN as a remote destination?

This will create 2 separate call legs that CUCM will independently manage.

/wes

On Feb 1, 2012, at 7:21 AM, Anthony Kouloglou wrote:

Hi all,
i am facing the problem where all incoming calls in a CUCME are ringing at the same time two devices but at some point, the company wants to have a call-forward all function enabled by one ( or both devices).

1. When i use parallel voice hunt group, call forward-all on any device does nothing (known issue)
2. When i use a third dn, overlay it to both devices in order to ring at the same time, call-forward all works only on the first dn
3. When i use the same secondary number on both dns, they have the same preference so they ring randomly.

Has anyone solved this puzzle?

Best Regards
Anthony

_______________________________________________
cisco-voip mailing list
cisco-voip <at> puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Unity and UCM would email me if an error occurred (backups missed, or some critical service died, or whatnot).
We changed email servers, so I need to login to those bad boys and give them the new server info...
I just can't seem to find where this is done.

Appreciate any help.

Dave

Jason,

This started with CUCM 7.X and Internal Services Provisioning. There is a special internal service that the phones use that they get from the TFTP config file. This service is a shortcut that says "Use the service from the server you're registered to" for things like corporate directory.

Check out the attached image so you can see the shortcut service.

You can switch the Phone Services Provisioning back to the old way of "External". This is configurable on the phone, or as an enterprise/service parameter (I don't remember which). The new way is better for load balancing though (for services that do reach out to servers) so I'd recommend sticking with it and just fixing the TFTP access.

For something like missed calls the phone wouldn't need to visit a CUCM server, but since the phone uses the new Internal Services Provisioning it's going to rely on what's configured in the TFTP file before it shows that Directory. There is probably room for improvement here though. The phone should fail back to  something else if available in flash when TFTP fails.

Does that explain it well enough?

-Jason Burns

Use the Real Time Monitoring Tool to connect into these servers and set your notification destinations / email servers. System > Tools > Alert > Config Email Server.