[VoIP] Missed Calls

[Doug Alderdice]

At 12:46 PM 5/3/2007 -0500, you wrote:
>John,
>
>Thanks.  That was definitely missing.  I added the port but need a few 
>"cold calls" to test it.  (If you try it before 5:00 PM, don't call a 
>human as my wife doesn't usually answer CNET calls.)
>
>PDW

Milliwatt line worked fine from the 366/833 exchange just now.

D.




> >From: "John R. Covert" <john_reads_cnet_via_archives at covert.org>
> >Date: 2007/05/03 Thu PM 12:19:50 CDT
> >To: CNET <voip at ckts.info>
> >Subject: [VoIP] Missed Calls
>
> >The behaviour Paul describes is exactly what would happen if his
> >IAX2 port isn't forwarded.  Callers would attempt to connect to
> >port 4569 at his firewall, which would ignore all calls (that
> >explains the "Max retries exceeded" message John Novack reported).
> >
> >However, if there had recently been an outbound IAX2 call to the
> >address of another CNET member, when that member calls back, the
> >firewall would still have the IAX2 port open.
> >
> >Lee wrote:
> >
> >>5060 - SIP (I forward TCP/UDP since I can't remember which it is)
> >
> >SIP can be done with either, but it's universally done only with UDP.
> >CNET doesn't use SIP.
> >
> >>4569 - IAX2 - UDP
> >
> >This is the main requirement for CNET.
> >
> >>10000 - 20000 - RTP - UDP
> >
> >But only if using SIP.  On IAX2 everything goes on 4569.
> >
> >>5036 - IAX - UDP
> >
> >No one uses this anymore.
> >
> >/john