search for: 02080

Displaying 4 results from an estimated 4 matches for "02080".

Did you mean: 0200
2009 Jan 20
2
SIP DTMF problem with SNOM
...s 4066340168, len 000004, mark 0, event 00000002, end 0, duration 01440) Got RTP packet from 83.136.33.3:64118 (type 101, seq 042822, ts 4066340168, len 000004) Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq 042822, ts 4066340168, len 000004, mark 0, event 00000002, end 1, duration 02080) Got RTP packet from 83.136.33.3:64118 (type 101, seq 042822, ts 4066340168, len 000004) Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq 042822, ts 4066340168, len 000004, mark 0, event 00000002, end 1, duration 02080) Got RTP packet from 83.136.33.3:64118 (type 101, seq 042822,...
2012 Feb 25
0
No IVR audio. Jump in RTP sequence number
...type 101, seq 042360, ts 175520, len 000004, mark 0, event 00000006, end 0, duration 01920) Got RTP packet from x.x.x.x:22760 (type 101, seq 042361, ts 175520, len 000004) Got RTP RFC2833 from x.x.x.x:22760 (type 101, seq 042361, ts 175520, len 000004, mark 0, event 00000006, end 1, duration 02080) <SIP/STARMG1-000003c5>AGI Tx >> 200 result=543278456 Got RTP packet from x.x.x.x:22760 (type 101, seq 042362, ts 175520, len 000004) Got RTP RFC2833 from x.x.x.x:22760 (type 101, seq 042362, ts 175520, len 000004, mark 0, event 00000006, end 1, duration 02080) Got RTP packet fr...
2010 May 28
1
[LLVMdev] Assertion when loading bitcode
...t;To, From>::ret_type llvm::cast(const Y&) [with X = llvm::FunctionType, Y = const llvm::Type*]: Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed. I think it happens because R->ParseBitcode() (lib/Bitcode/Reader/Bitcode.cpp 02080) fails which causes line 02086 to be executed??? Has anyone come across this problem before? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100528/adcea9f3/attachment.html>
2009 Jan 20
5
the FXS ports of Digium and damaging if connected to Tel Line
Hi All; I am facing a problem that always the users confused and connect the telephone line coming from the telephone service provider to the FXS port and cause it to be damaged, specially if the card was 2 fxs and 2 fxo, so they make mistake and connect the line to fxs while it should be connected to fxo. What is the solution for this disaster? Regards Bilal