[cisco-voip] H323 Gateway needed for SNR mid-call features?

[Lelio Fulgenzi]

that's all i needed to hear. ;) 

thanks, Lelio 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Wes Sisk" <wsisk at cisco.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "Nate VanMaren" <VanMarenNP at ldschurch.org>, "cisco-voip at puck.nether.net VOIP" <cisco-voip at puck.nether.net> 
Sent: Friday, March 9, 2012 11:49:55 AM 
Subject: Re: [cisco-voip] H323 Gateway needed for SNR mid-call features? 

It's been tried and it leads to interesting scenarios. invoking features like transfer utilize the h323/sip router's dialplan rather than CUCM's. Then you configure peers to route to CUCM. IF you're tandeming through CUCM to get the h.323 gateway then you tandem back to cucm so you need ip-ip-gw functionality. then you have issues with SNR dial-peers overlapping/conflicting with SRST dial-peers. That leads to some interesting COR configuration. Down the rabbit hole. 


It was a fun lab and whiteboard session with several CCIE's. It could be made to work with numerous limitations. it's possible but may not be recommended for the masses without some very careful design and functionality choices. 


/wes 




On Mar 9, 2012, at 11:31 AM, Lelio Fulgenzi wrote: 


wonder if i could run the hairpinning on the same router that has the MGCP gateways. that would probably screw up any chance of getting SRST working without confusion though. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Nate VanMaren" < VanMarenNP at ldschurch.org > 
To: "Wes Sisk" < wsisk at cisco.com >, "Lelio Fulgenzi" < lelio at uoguelph.ca > 
Cc: " cisco-voip at puck.nether.net VOIP" < cisco-voip at puck.nether.net > 
Sent: Friday, March 9, 2012 11:02:23 AM 
Subject: RE: [cisco-voip] H323 Gateway needed for SNR mid-call features? 



I think SIP is ok too. Basically no MGCP because it can’t do the tcl/vxml. 




From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Wes Sisk 
Sent: Friday, March 09, 2012 8:50 AM 
To: Lelio Fulgenzi 
Cc: cisco-voip at puck.nether.net VOIP 
Subject: Re: [cisco-voip] H323 Gateway needed for SNR mid-call features? 


my vague recollection is yes. mid call features depend on the h323 gateway listening in on the call and invoking a tcl or vxml script (increasing fuzziness here). 





On Mar 9, 2012, at 10:00 AM, Lelio Fulgenzi wrote: 






OK, I'm pretty sure this is the case, but I'm just wondering if someone can confirm/deny. 

Do I need an H323 gateway for SNR mid-call features? 

The document talks about using H323 for mobile voice access, but I'm just wondering if this is a per-requisite for mid-call features like transfer, etc. 

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmfeat/fsmobmgr.pdf 

Thanks, Lelio 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


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





NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120309/50c2ba3d/attachment.html>