이성우 wrote:
> Dear
>
> Have you ever experienced cases that you can not receive any rtp packets even 
> after finishing offer/answer negotiation is done, and can receive packets 
> only after sending out your first to the remote party? Provided there is no 
> fault in SIP signaling perspective, in what circumstances could we possibly 
> meet cases like this? Wouldn't be NAT configuration or SBC policy in SIP 
> carrier side? If so, will there be any specific reasons for this?
>
> happy holiday.
>
> Lee, Sungwoo
>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
>
>   
You can use Niksun's NetVoice for monitoring your sip Network and find 
out the bottleneck

Key Benefits

* End-to-end proactive network and application performance
* High-speed non-intrusive complete or filtered VoIP recording, analysis 
and audio/video playback
* Collects, records and analyzes virtually unlimited calls
* Analyzes data with time resolution down to the microsecond
* Completely correlated call to message to packet level analysis
* Complete call level QoS details: Delay, Loss, Jitter and MOS score
* Powerful analysis and filtering for real-time remote diagnostics

For more details http://www.niksun.com/product.php?id=6 .

Regards,
Mayank Jain
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to