Code to wire cut during packet switching

Question

3.00/5 (1 vote)

See more:

I am sending packet from DSLAM to modem.Packets are UDP.If in case transmission gets over suddenly we should know weather it is because of modem being off or wire cut.It is a problem we face in IPTV.

Posted 2-Feb-10 23:07pm

Navpret

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

#realJSOP · Answer 1 · 2010-02-02T23:36:00

Solution 1

There's no earthly way you can determine why the connection dropped. You can only determine that it did in fact drop.

Posted 2-Feb-10 23:36pm

#realJSOP

Moak · Answer 2 · 2010-02-03T01:27:00

UDP does not have a built-in connectivity status, when switching to TCP is not feasible then here are two other alternatives:

1) You might want to add a connectivity test to your application. For example test in regular interval if a service (on the internet) is still available.

2) If you do not have a kind of connectivity status to use, then add one by implementing a reasonable fast heartbeat in your own application. If peer A wants to know about the status/availability of peer B, it either has to receive a "message" from B in regular intervals (and therfor knows that peer B is alive) -or- when there is no regular traffic to piggyback the heartbeat then one of the peers has to initiate (additional) heartbeats in reasonable intervals. For example an IRC server uses regular ping/pong messages every few minutes to find out about the connection status of its chat clients.