cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Walkthrough Wednesday: Flexible PSTN options for your Webex Calling deployment - EVENT Q&A

207
Views
0
Helpful
2
Comments

Q: Will this deck be made available?
Cole Callahan - 13:09
A: Yes, it will be posted in the Webex Community following the event
________________________________________________________________

Q: Maximum of one Connection type per Location ?
Johannes Krohn - 13:10
A: Yes, the PSTN connectivity for each location is either Cisco Calling Plan, Cloud Connected PSTN, or premises trunk
________________________________________________________________

Q: Is the Cisco Calling plan compatible with existing PSALI services that I subscribe to?
Ed Schermerhorn - 13:15
A: Cisco Calling plan meets all regulatory requirements for connecting to PSAP. If you have additional functions occuring on your PSTN link for calls to emergency services, those would need to be explored
________________________________________________________________

Q: What´s the ETA of the calling plans in Europe?
Ed Schermerhorn - 13:17
A: We will be rolling out to select EU countries later this year as the initial phase.
________________________________________________________________

Q: How do I quote these services? Provisioning is only needed after the customer has purchased. 
Johannes Krohn - 13:35
A: See the ordering guide: https://www.cisco.com/c/en/us/products/collateral/unified-communications/spark-flex-plan/collaboration-flex-plan3-og.html
________________________________________________________________

Q: Can I mask outbound calls with a TN that is not part of my Cisco calling plan? I would like calls to be masked with our TN on our IP-PBX so returned calls come back in a different way.
Johannes Krohn - 13:18
A: No, the TN needs to be a valid TN in the Webex Calling location (has to be part of your Webex Calling Number set). You can port the number to Cisco Calling Plan though...
________________________________________________________________

Q: do we have access to the recording of this session ? 
Cole Callahan - 13:15
A: Yes, the recording will be posted in the Webex Community. Look at the chat above for the exact link. 
________________________________________________________________

Q: Is g729 supported for a WxC deployed in conjunction with WxCC? Does it require transcoding on the LGW?
Johannes Krohn - 13:32
A: What is the use case? PSTN call legs are G.711. Do you really want to transcode everything to G.729? Why? Bandwidth constraints?
________________________________________________________________

Q: Do you support CSR8000v?
Johannes Krohn - 13:19
A: See the ordering guide: https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-border-element/guide-c07-742037.html
________________________________________________________________

Q: So no ASR support 
Johannes Krohn - 13:20
A:  See the ordering guide: https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-border-element/guide-c07-742037.html
________________________________________________________________

Q: Theres sir charges (per minute fees) associated with Cisco PSTN SKU's..please explained

Ed Schermerhorn - 13:25
A: The Cisco Calling Plan has different levels of calling usage (up to unlimited long distance)
________________________________________________________________

Q: Licenses must be ordered separately -- this is for the cube base only? Sip sessions can be used in 2:1 ratio from licensed users, or has that changed?
Johannes Krohn - 13:21
A: For details check the Local Gateway Ordering Guide: See the ordering guide: https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-border-element/guide-c07-742037.html
Johannes Krohn - 13:22
A: the 2:1 ratio still applies
________________________________________________________________

Q: does that 200k get reduced to 100k with ICE/TURN ?
Ed Schermerhorn - 13:21
A: Remember that services like confrence, music on Hold, etc will still require media from the cloud.
________________________________________________________________

Q: Are there plans to enable peering to avoid 250 limit?
Johannes Krohn - 13:22
A: You can peer via Webex Edge Connect and then the limit goes up to 500
________________________________________________________________

Q: Is the 250 call limit describe somewhere in documentation 
Johannes Krohn - 13:22
A: Yes
________________________________________________________________

Q: If the LGW is used for multiple WxC sites, it is able to handle 250 per site as these have seperate registrations?
Johannes Krohn - 13:24
A: Correct. The concurrent calls limit is for all calls sharing the fate of a single TLS connection. If you configure multiple instances and bind them to different IP addresses (loopback or sub-interface) then you can have n x 250 sessions on a single platform.
Johannes Krohn - 13:25
A: .. keep in mind that CUBE HA won't work w/ loopbacks. With multiple platforms you can still improve scale and redundancy by using route groups.
________________________________________________________________

Q: Regarding the 250 max calls - I am assuming that this is the case for the new webex calling Plans, correct?
Johannes Krohn - 13:26
A: That limit DOES NOT apply to Cisco Calling Plans. The # of concurrent calls per Local Gateway is limited to 250.
________________________________________________________________

Q: Q: Will Webex Calling support/use peering agreements, namely Internet2?
Johannes Krohn - 13:27
A: First peering option is to use Webex Edge Connect. The Webex Calling IP prefixes are part of the BGP advertisements on Webex Edge Connect.
________________________________________________________________

Q: Can we configure the LGW for just extension to extension dialing, from WxC to IP PBX and then use Cisco Calling Plan for PSTN?
Johannes Krohn - 13:29
A: Yes, see https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/Collaboration/hybrid/AltDesigns/PA-WbxCall.pdf for details. In short: use Cisco Calling Plan for PSTN and configure dial plans in Webex Calling to define which on-net destinations should be routed to a premises trunk
________________________________________________________________

Q: Not sure my question was answered fully. So, ICE/TURN, if direct media is established with the phone, you only need to account for 100k unless the phone does a hold or conference? correct?
Ed Schermerhorn - 13:30
A: If the call in between end stations, yes the calling media payload between calls would not traverse the internet link
________________________________________________________________

Q: Does WebEx Calling have work with or have a similar product such as Oracle's Communications Operations Monitor / EOM?
Ed Schermerhorn - 13:46
A: I am not familiar with that solution, but if you want to reach out 1:1 to explore further, please message me at escherme@cisco.com
________________________________________________________________

Q: Follow up: I've a vCUBE with only two interfaces. There are two tenants facing WxC, both connected to different PSTN providers. They share the same two interfaces (both are even private and share the same public ip), routing is done by E164 prefix. So based on your statement, they will share the 250 calls as they use the same interfaces/addresses?
Johannes Krohn - 13:31
A: Yes, unless you configure multiple LGW instances.
________________________________________________________________

Q: No controls on Webex side? What stops customers to put more than 250 there?
Johannes Krohn - 13:38
A: The Webex Calling backend enforces a llimit. 
________________________________________________________________

Q: If you do multiple instances on a single platform, you are still bound to the documented Calls Per Second, correct. So, CPS is a limit of the platform, not the TLS connection per se ?
Johannes Krohn - 13:39
A: Yes. You need to differentiate between concurrent session limit driven by TCP performance and overall platform capacity.
________________________________________________________________

Q: when you deploy WxC with LGW as the PSTN/PBX for the WxCC integration
Johannes Krohn - 13:38
A: As far as the topic of this session is concerned: yes, G.729 absolutely can be used end-to-end through Local Gateway to Webex Calling. For the Webex Contact Center part I need to defer the question to a Webex Contact Center colleague.
________________________________________________________________

Q: just to clarify when we say 250 calls for an LGW,, does that include both call legs for a single call. I see "calls" and "sessions" used in this context - not sure what we mean by sessions. Because 250 calls can usually be 500 call legs
Johannes Krohn - 13:45
A: 250 concurrent CALLS. A CALL through LGW has an incoming and an outgoing call leg. 
________________________________________________________________

Q: Just a general comment: In all WxC trainings, it's basically "take this template, paste your registration data and it will work. In practice, there are always some pitfalls with DIP headers required by the PSTN provider/WxC. A course focusing on special configurations like sip translations, dial peers etc. would be great!
Johannes Krohn - 13:47
A: Great feedback
________________________________________________________________

Q: What about ICE? It is supported for LGW, right?
Johannes Krohn - 13:46
A: CUBE supports ICE lite
________________________________________________________________

Q: Are these options available in Webex calling 1: Customized scripts for IVR for TFN 2: call recording

A: Customized scripts for IVR are not supported on the local gateway or for call recording.
________________________________________________________________

Q: so if we do not want the PAI to override the From field for caller ID we should not enable PAI on any of the dial-peers?

A: Webex calling requires PAI to be enabled as that is the only identity header supported. The SIP profile is the only option as discussed during the session.

Comments
Ronen Benjamin
Beginner

Thanks , I had the same issues

ronen

Cole Callahan
Cisco Employee

Happy to hear it was useful for you @Ronen Benjamin !

Content for Community-Ad