[cisco-voip] TIP: CNAM without requiring MGCP

[Wes Sisk]

CTI still does not support 2833, so if you have any CTI endpoints  
you're going to need MTP or DSP resource if low bitrate.

/Wes

On Oct 13, 2006, at 8:20 PM, 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.



In one of those “why didn’t I think of that before” moments, one of  
my colleagues thought to test connectivity using an incoming SIP dial  
peer and SIP trunk on call manager.  Lo and behold, CNAM works  
perfectly!  H.323 dial peers can still be used as needed to match  
other inbound and outbound traffic, and since the routing decisions  
are being done at the gateway, TCL scripts can still be used.



A few SIP specific parameters are required on the gateway including:



signaling forward unconditional

sip

   bind all source-interface <interface>

!

!

sip-ua

   timers buffer-invite 5000



As well as adding “ session protocol sipv2 “ to the incoming voip  
dial-peer.





Configuration on Call Manager includes adding an RFC 2833 DTMF- 
compliant MTP resource and setting up a SIP Trunk to the gateway.





While we have not fully tested this configuration, it appears to  
solve the problem of not being able to receive caller-id name  
information while still maintaining gateway based call routing.



Can anyone point to any problems we might encounter with this setup?







David Zilk




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.

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061015/929f5f87/attachment-0001.html