Displaying 20 results from an estimated 1000 matches similar to: "Asterisk terminates unexpectedly with SIP call and G.723 codec"
2004 Jul 09
3
ATA 186, firmware SIP 3.1 and codec g.726
I have a ATA 186 with SIP firmware 3.1 when I changed the configurations to
use the g.726 codec I received many erros and the calls doesn't work.
I changed the fields:
- LBRCodec: 6 <- the code for g.726
- TXCodec: 6
- RxCodec: 6
The errors:
Jul 9 13:15:37 NOTICE[1192491824]: rtp.c:500 ast_rtp_read: Unable to
calculate samples for format G726
Jul 9 13:15:37 NOTICE[1192491824]:
2003 Sep 11
1
g729 codex experimentation
Yesterday, I started to experiment with Cisco to Cisco SIP calls using
the g729 codec. According to the documentation, both the ATA-186 and
7960 are able to make use of the g729.
>From an earlier e-mail, I made a change to the configuration of the ATA,
changing the values:
LBRCodec:3
RxCodec: 3
TxCodec: 3
The first thing I noticed was that when I did a sip show channels, the
format had
2005 May 10
3
MGCP : chan_mgcp.c:1509 find_subchannel
When I try to connect to * using a Cisco ATA 188 configured with a MGPC firmware (v3.1.1), I just
keep getting this message every 30 seconds or so :
May 10 10:08:21 NOTICE[7913]: chan_mgcp.c:1509 find_subchannel: Gateway '192.168.1.27' (and thus its
endpoint '*') does not exist
Using tcpdump, I have checked that the ATA188 (with IP 192.168.1.27 and port 2427) sends UDP packets
to
2004 Jun 23
0
connecting to Iconnect here using asterisk
Hi,
I wish to connect several ATA186 Phones to each other, to iconnecthere and
to the PSTN using asterisk.
Please tell the appropriate settings for firewall (ports to open etc.)
sip.conf and extensions.conf(part relevant to iconnect).
Also I would be glad to get a working example of your ATA186 configuration.
I tried searching the mailing lists and several sites but did not find an
answer.
2004 Jun 03
4
miserable time with Cisco ATA186
I'm having a horrible experience getting a Cisco ATA-186 to work with *.
I can make calls from the ATA with no problems. However, incoming calls
make the ATA ring once, and then the call is disconnected. I have no
problems with my Sipura 2000 or my Grandstream phones.
I am running 2.16.1 sip code on the ATA 186. Neither * nor the ATA is
behind a NAT. They are both on public IP addresses
2003 Dec 22
1
Fw: Questions and finding
I installed * to primarily test its voicemail feature. I installed it on a server WITHOUT any telco board (i.e., digium). Installation looks ok, however I am having problems.
MY SETUP:
2xATAs are configured to use * as GkorProxy
Asterisk is registered to my SER SIP/RTP Proxy
1.) First test
- ATA1 calls to ATA2. When voicemail starts playing, it just cuts-off after 5-10seconds (consistently).
2004 Jul 09
1
RE: ATA 186, firmware SIP 3.1 and codec g.726 + now SIPURA SPA-2000
To me it's a error if I can't complete calls using the ATA configured to use
the g726 codec.
I just tried it usign a sipura SPA-2000 (preferred codec: G726-32) and I
received NOTICES and WARNINGS, but I can't complete a call.
On a zap channel:
-- Executing Dial("SIP/2007-e4d8", "Zap/1/2217008") in new stack
-- Called 1/2217008
-- Zap/1-1 answered
2003 Jun 04
5
RTP codec error???
When I make a call using sip, I get the line
NOTICE[327696]: File rtp.c, Line 292 (ast_rtp_read): Unknown RTP codec
19 received
Repeated many times on the console
; SIP Configuration for Asterisk
;
[general]
port = 5060 ; Port to bind to
;bindaddr = 0.0.0.0 ; Address to bind to
context = outgoing ; Default for incoming calls
allow=gsm
allow=ulaw
2003 Nov 05
1
iconnect
Hi,
I was able to connect asterisk to iconnect's service.
It took me almost two hours, but it's because I was having NAT trouble.
I finally discovered that you can set the iconnect host to
natrealy.deltathree.com to make it work.
(for those of you who, like me, don't have the time to search the
archive I'll provide a working sample in a minute)
My problem was sound
2004 Aug 10
0
iconnect inbound - FIXED (kinda)
This appears to have been the magic bullet for me.
Thank you very much.
So, the bottom line is that there is a bug that ends up making inbound
calls use type=peer rather than type=user.
Correct?
> -----Original Message-----
> From: asterisk-users-admin@lists.digium.com
> [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Paul Cheng
> Sent: Tuesday, August 10, 2004 8:35
2003 Dec 12
1
simple question on sip.conf
Hi folks,
I want to fix hole in my asterisk set up.
I use Vocal as my sip proxy and * for voice mail and the g/w to PSTN,
Iconnect, fwd etc. So from Vocal I redirect sip requests which needs to go
'other' places. This senario works fine.
Now the issue is someone else running a vocal or another SIP proxy can
redirect his calls to my * as well. Those calls two will come through
general
2003 Nov 19
2
g723 to g723 SIP call - warning message
Hi,
I am calling from a grandstream phone with g723 codec through * to iconnect.
Incoming context as well as outgoing context set to g723.1 codec in *.
Call get connected and I can talk. However I get the following warning,
which scrolls on my screen until I hang-up.
[root@asterisk sath]# cat g723.1
- Executing SetCallerID("SIP/-08122ae0", "1001") in new stack
--
2004 Aug 04
0
New Head Appears to Break SIP to iConnect
Folks,
I have to admit that I MAY have changed something (at someone's
advice) on a previous CVS head (May 28), but I'm not sure. I think that
it had to do with changing "digest realm," but that may be a different
issue. At any rate, I had both incoming and outgoing with iConnectHere.
Now, I made exactly ONE change: I upgraded to the CVS head
dated 7/30. I
2003 Mar 09
6
DTMF detection on SIP provider ?
Hi..
I just wondering why DTMF are not recognized by aterisk on incoming calls
from my SIP provider ...
ANy suggesteions ?`
/Mike
2003 Mar 03
3
iconnecthere 480 error: is there a workaround?
I am going to have to find a fix for this problem or I'm going to have
to quit using iconnect.
About one call in 10 or so, iconnect's gateway gives me an error
(console output appended below).
So upon receiving the error, which as a 4XX error means, "Fatal,"
asterisk gives up and drops the call. But not iconnect!! The phone at
the other end starts ringing, and rings
2004 Jan 09
0
IConnect audio quality
Hello,
I've subscribbed to "IConnect". I use it eclusively for outbound
calling. I like the rates they charge but people I call complain about
the audio quality. They say it sounds like I'm using a "cheap mic." or
they
complain about echo. The sound is very clean at my end. I'm using
a Bundgtone phone with meadi routed through Asterisk to IConnect.
It's
2003 May 18
2
G.729: Typical usage scenarios
Clicking on the "For more information, click here" link on the Digium
site nice brings back up the same page I was looking at before, without
any additional G.729 information that I can see.
I'm wondering if some kind asterisker out there could provide us
neophytes with some "typical scenarios" where that codec would be useful
to us.
For instance, I assume that it
2004 Sep 30
0
Asterisk seems to have more jitter than a hardphone with SIP
I have an asterisk Redhat 9 box running 4 hardphone extensions.
Inter-extension calls are crystal clear.
However when I dial out through my iconnect account I get a lot of jitter.
At first I thought it was my nat gateway but after I programmed on of the
hardphones (budge tone 100) for direct dial to iconnect I have clear voice
transmission.
I have no way of explaining this.
My asterisk sip.conf
2004 Jan 23
3
RFC3389 support issue with DG104S
I am getting (with older image):
RFC3389 support incomplete. Turn off on client if possible
How do I turn that off for the DG104s? Or if I can't how do I tweak
asterisk?
I see posts about ATA-186's having an audiomode, but the closet I came
to was inbanddtmf. I tried =0 and =1, no effect.
Thanks!
--
Zot O'Connor <zot@zotconsulting.com>
White Knight Hackers, Inc.
2004 Apr 30
1
sip notify from iconnect
Hello,
Recently I am seeing this message on my asterisk console received from
Iconnect.
Apr 30 11:37:21 NOTICE[1125329600]: chan_sip.c:5648 handle_request: Unknown
SIP command 'NOTIFY' from '213.137.73.41'
It is prety annoying as it appears once every four seconds.
I've seen similar posts in the archives which points me to NAT keep alives
being send by the remote end. I am