[cisco-voip] TIP: CNAM without requiring MGCP

[Zilk, David]

We have not tested call preservation yet.  It is on the plate though.
If there are any issues, I will let the group know.

David

|-----Original Message-----
|From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-
|bounces at puck.nether.net] On Behalf Of Robert Kulagowski
|Sent: Monday, October 16, 2006 8:52 AM
|To: cisco-voip at puck.nether.net
|Subject: Re: [cisco-voip] TIP: CNAM without requiring MGCP
|
|Zilk, David wrote:
|> Many of you have run across the problem of not being able to utilize
|> Caller ID Name (CNAM) information from a telco using H.323.  Since
CNAM
|> is provided by most telcos  within the facility IE field, and this
isn't
|> supported in H.323, the solution has always been to convert to MGCP.
|>   If you needed to stick with H.323 or gateway based call routing for
|> other reasons, such as needing to support other H.323 devices, or use
|> TCL scripts, you were out of luck.
|
|Have you tested called call preservation?  What happens if the WAN goes
|down during a call?  Is the call dropped?  That was the biggest reason
|we went to H.323 over MGCP.
|
|_______________________________________________
|cisco-voip mailing list
|cisco-voip at puck.nether.net
|https://puck.nether.net/mailman/listinfo/cisco-voip


This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.