Displaying 4 results from an estimated 4 matches for "00070ms".
Did you mean:
00000ms
2006 Jan 03
1
IAX2 channels denoted as '(None)'
...9;t be cleared by that method. Here is the output from
iax2 show channels:
*CLI> iax2 show channels
Channel Peer Username ID (Lo/Rem) Seq
(Tx/Rx) Lag Jitter JitBuf Format
(None) 111.111.111.111 xxxxxx 00003/00020
00001/00003 00070ms 0001ms 0071ms g729
(None) 111.111.111.111 xxxxxx 00004/00005
00004/00005 00070ms 0000ms 0070ms g729
(None) 111.111.111.111 zzzzzz 00005/00004
00002/00004 00000ms 0007ms 0071ms g729
(None) 111.111.111.111 xxxxxx...
2005 May 16
4
IAX jitter
..., for 2 of the users the
audio is fine, but for the 3rd user there is intermittent break up in the
audio when they are receiving. I have had a look at "iax2 show channels" and
for the first 2 users (those with no audio problems), the Jitter is low
(0006ms), and the Lag is relatively high (00070ms). For the 3rd user (the
one with audio breaking up), the Jitter is relatively high (0627ms) and the
Lag is relatively low compared to the others (00012ms).
All of the users are on the same LAN, so can't quite understand the
differences.
Any explanations / ideas would be much welcome....
2004 Dec 14
0
Codec "Uknown" with IAX connection
...Retry[000] -- OSeqno: 001 ISeqno: 002 Type: IAX Subclass:
ACCEPT
Timestamp: 00067ms SCall: 00003 DCall: 00025 [204.188.109.139:4569]
FORMAT : 4
-- SIP/5001-3f33 is ringing
Tx-Frame Retry[000] -- OSeqno: 002 ISeqno: 002 Type: CONTROL Subclass:
RINGING
Timestamp: 00070ms SCall: 00003 DCall: 00025 [204.188.109.139:4569]
Rx-Frame Retry[ No] -- OSeqno: 002 ISeqno: 002 Type: IAX Subclass: ACK
Timestamp: 00067ms SCall: 00025 DCall: 00003 [204.188.109.139:4569]
Rx-Frame Retry[ No] -- OSeqno: 002 ISeqno: 003 Type: IAX Subclass: ACK
Timestamp: 00070...
2007 Dec 11
2
Iax and ZAP
I have a working system with two fxo and two fxs channels. I recenlty got an IAX2 account I would like to use also.
While I have gotten the IAX2 channel to "register", it remains non functional, as the incoming calls, go nowhere and the outgoing calls attempt to go out over the ZAP channel. I can see this, via the CLI, with debugs on.
I strongly suspect this is a dial plan/config