Hi Anuj Nirala,
Since, the customer has not come back yet, we will proceed in closing this ticket for now.
Regards,
FVC Technical Support Team
On Tue, 24 Feb at 10:42 am , FVC Tech Support <[email protected]> wrote:"Customer removed from the loop"Hi Anuj,Further to our detailed explanation provided previously, kindly find attached the document which lists out all the call flow processes that happens before a call gets connected. Elaborate description of the issue as below:H.323 call made using Extension@domain ([email protected]):This is not the general format of making H.323 calls but it is still acceptable as if the systems involved can receive calls in this format, the calls would still connected.The H.323 call was made from our endpoint in DIC office registered with the RPAD there to an endpoint in our JLT office registered with our other infrastructure. Even though both are part of the same domain (dic.fvc.com & jlt.fvc.com), the call almost took 9 seconds to get connected as the systems still had to resolve the far end domain (which was quicker in this case since they're part of the same domain), but the capability exchange between them took most of the time.H.323 Call made using Public IP##Extension (5.32.38.165##104):
This is the general way in which H.323 calls are made and that's why if you see in the screenshots, the calls get connected within 2 secs.If the domain that the customer is trying is for an external party, then the resolution will take more time, and the capability exchange taking even more time, thus the additional 10 secs delay when compared to the calls made using the Public IP.Kindly note that this is how the working of H.323 protocol is defined in the RFC standards and hence this time difference observed will always be there in the connection of calls.Regards,FVC Technical Support Team
On Mon, 23 Feb at 1:04 pm , Anuj Nirala <[email protected]> wrote:Dear Support Team,Please do share more information on this.This Query is still open, Please help for close loop.Thanks & RegardsAnuj Kumar NiralaMob: +974 – 5033 7309Email: [email protected]Keep Emails On-screen. Please consider the environment before printing. At QDS we support conservation.From: Anuj Nirala
Sent: Monday, February 16, 2015 1:11 PM
To: 'FVC Tech Support'
Cc: [email protected]; Faraz Qureshi; Adnan Al-Khmour
Subject: RE: RE: External SIP Call further testing. 26@11AM (Resolved)Hi TeamAs discussed with Firas, below response is not ok for him.Even during the testing the same format call from FVC to Beinsports was Quick compare to Beinsports to FVC.Please do share more information on this.Thanks & RegardsAnuj Kumar NiralaMob: +974 – 5033 7309Email: [email protected]Keep Emails On-screen. Please consider the environment before printing. At QDS we support conservation.From: FVC Tech Support [mailto:[email protected]]
Sent: Sunday, February 15, 2015 10:11 AM
To: Anuj Nirala
Cc: [email protected]; Faraz Qureshi; Adnan Al-Khmour
Subject: Re: RE: External SIP Call further testing. 26@11AM (Resolved)-------------------------------------------------------------------------------------------------------------------------- This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of this e-mail communication or any part of it by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissionsHi Anuj,We were all also trying to make the calls locally and we also noticed a similar delay for the calls to get connected, the reason found based on the logs as below:Generally, H.323 calls are made using the format Public IP##Extension.But the other format of extension@domain format is still supported, but takes longer as there are additional steps involved as mentioned below compared to the previous method:a. Domain Name -> Public IP resolution via the Public DNS Serverb. Capability negotiation and exchange with the far end system in place to check if the format is accepted for H.323 calling, as certain steps accept this type of calls only for SIP and not H.323Hence, the delay for the call establishment.Whereas, since for SIP calls are generally made as extension@domain or systemname@domain, the capability negotiation and exchange is immediate, because of which the call establishment is faster.Kindly let us know if you still have any further queries.Regards,FVC Technical Support TeamOn Sun, 15 Feb at 10:27 am , FVC Tech Support <[email protected]> wrote:Hi Anuj,We are looking into the below and will get back to you in ah hour.Regards,FVC Technical Support Team5127