Are you referring to B2B calls, like the VBP E box? If so, yes. We've tested here on 3.0 & SIP/H.323 outbound calls are working. The only issue we are having is with registrations using creds either via RP Desktop, RP Mobile or CMA Desktop. RPD & RPM show "invalid server address" (either using the IP address or the DNS name).
My scenario is a hosted model xyz. A End Point X gets registartion from Internet via RPAD. Now, End Point X wants to dial a End POint Y which is not registered to the hosted network and is on a public IP. Can this be done? Please note the call flow will be as below:
EP X to RPAD, RPAD to DMA, DMA to RPAD, RPAD to EP Y.
RPAD 3.0 is giving lots of issues.
Has anyone tried RPAD 3.0 and registered two internet end points (makes a scenario of hosted service provider) and tested all call features? If yes share your experience.
In my opinion, RPAD is not yet certified for a service provider enviornment.
Does RPAD have any way to act as a LAN side GK like VBP did? This would be a nice feature especially in very small deployments before adding a DMA.
@Don - no - the RPAD does not have the LAN side GK functionality in v3. Not sure if this is one the road map or not.
@Kundan - I would have to agree with you on that SP statement. we still have some more work to do. There is an issue dialing out via SIP because the RPAD checks to see if the SIP call is in the list of neighbored B2B domains and ultimately drops the call. However, h323 works in your setup just fine.