similar to: Choosing codecs

Displaying 20 results from an estimated 900 matches similar to: "Choosing codecs"

2015 Jul 05
2
Choosing codecs
Hi list! I noticed that when the phone of my wife calls the gsm codec will be used, but if someone calls the phone, alaw will be used: 00493511111111 calls 00493512222222: OpenWrt*CLI> sip show channels Peer User/ANR Call ID Format Hold Last Message Expiry Peer 192.168.200.11 00493512222222 5305ad0e07977dd 0x4 (ulaw) No
2015 May 29
0
Calling from "extern"
Hi list! Finally I got my wife's phone working in my Asterisk. Unfortunately I have some problems, too... Current situation: - AsteriskNOW with 4 Accounts (00493511111111, 00493512222222, 00493513333333, 5678). This is "for test" and it will be replaced by "the real world", when I got my Asterisk to work... - A second Asterisk (Ubuntu-PBX) on another VM, logging in
2015 May 28
4
Peer is UNREACHABLE
Hi list! I have a problem and I hope someone can help me... I configured an Asterisk on a VM to serve more accounts and act as a proxy to other SIP-providers. The first account running on my phone works without any problem. A second account, running on the phone of my wife, is always UNREACHABLE. I can just see in the log: [May 28 21:48:46] NOTICE[3646]: chan_sip.c:22933 sip_poke_noanswer: Peer
2020 Jun 13
0
Voice "broken" during calls
So the call used Alaw as Codec. > Am 13.06.2020 um 17:23 schrieb Luca Bertoncello <lucabert at lucabert.de>: > > Am 13.06.2020 um 13:47 schrieb Michael Keuter: > > Hi > >> Try "sip show peer <peername>" for a phone. > > So: > > mobile phone: > bpi*CLI> sip show peer 0049177xxxxxxx > > > > > * Name :
2015 May 28
0
Peer is UNREACHABLE
> I have a problem and I hope someone can help me... > I configured an Asterisk on a VM to serve more accounts and act as a proxy to > other SIP-providers. > > The first account running on my phone works without any problem. > A second account, running on the phone of my wife, is always UNREACHABLE. > I can just see in the log: > > [May 28 21:48:46] NOTICE[3646]:
2015 May 28
0
Peer is UNREACHABLE
I'd start by turning on sip debugging in asterisk >sip set debug ip [your_phone_ip] and use tcpdump or wireshark to see what the OS sees tcpdump host [your_phone_ip] and udp port 5060 On 15-05-28 03:58 PM, Luca Bertoncello wrote: > Hi list! > > I have a problem and I hope someone can help me... > I configured an Asterisk on a VM to serve more accounts and act as a proxy
2020 Jun 13
5
Voice "broken" during calls
Am 13.06.2020 um 13:47 schrieb Michael Keuter: Hi > Try "sip show peer <peername>" for a phone. So: mobile phone: bpi*CLI> sip show peer 0049177xxxxxxx * Name : 0049177xxxxxxx Description : Secret : <Set> MD5Secret : <Not set> Remote Secret: <Not set> Context : default Record On feature : automon
2015 May 28
3
Peer is UNREACHABLE
Darryl Moore <darryl at moores.ca> schrieb: > Ahh. Seen that before! That suggests to me that you don't have your > sip.conf records setup right. > > What's your sip.conf look like? Well, here what I wrote in my sip.conf: register => 00493511111111:MYSECRET at pbxluca/00493511111111 register => 00493512222222:MYSECRET at pbxfax/00493512222222 register =>
2015 May 28
0
Peer is UNREACHABLE
I think your phone may be trying to register with the username '1234', while your sip configuration is expecting 'luca'. Can you try changing your phone registration credentials to use 'luca'? Can you give us a sip transcript when you try to place a call from it? On 15-05-28 05:09 PM, Luca Bertoncello wrote: > Darryl Moore <darryl at moores.ca> schrieb: >
2015 May 31
2
Signaling incoming call
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guenther Boelter <gboelter at gmail.com> schrieb: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 05/31/2015 02:31 PM, Luca Bertoncello wrote: > > Hi list! > > > > Now all works as expected, at least in the simulation I did with > > AsteriskNOW. Hopefully it will work later, when Deutsche Telekom
2015 May 28
4
Peer is UNREACHABLE
Darryl Moore <darryl at moores.ca> schrieb: > I'd start by turning on sip debugging in asterisk > >sip set debug ip [your_phone_ip] Really destroying SIP dialog '490d1996593c8e11217828b71aae5c4d at 172.16.34.133' Method: OPTIONS Reliably Transmitting (no NAT) to 192.168.200.11:5060: OPTIONS sip:00493512222222 at 192.168.200.11:5060 SIP/2.0 Via: SIP/2.0/UDP
2015 May 28
0
Peer is UNREACHABLE
> Darryl Moore <darryl at moores.ca> schrieb: > > > I'd start by turning on sip debugging in asterisk > > >sip set debug ip [your_phone_ip] > > Really destroying SIP dialog '490d1996593c8e11217828b71aae5c4d at 172. > 16.34.133' Method: OPTIONS > Reliably Transmitting (no NAT) to 192.168.200.11:5060: > OPTIONS sip:00493512222222 at
2003 Feb 03
1
Problems booting PXE-Client
Hi list, I have installed DHCP, PXE and the TFTP-Server tftp-hpa. I'm running Debian Woody on my server and I want to boot a PXE-Client with this server. I have installed all as it is described in the docs found on the net. Under root: /tftpboot/ /tftpboot/X86PC/linux /tftpboot/X86PC/linux/messages /tftpboot/X86PC/linux/linux.0 /tftpboot/X86PC/linux/vmlinuz
2009 Jun 05
3
R: Re: R: Re: PXEbooting very slow
I made other tests. It's not a matter of Win98 versus WinXP, things change passing from tftpd32 v310beta to v3.33. This version seems to work fine, but the logs show problems. Here is the complete log with pxelinux 3.82-pre4: Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:1E: 68:A6:9E:A9 [05/06 18:24:43.816] DHCP: proposed address 192.168.1.20 [05/06 18:24:43.816] 1356 Request 2 not
2015 Dec 30
2
Signaling ringing on other extension
Ishfaq Malik <ish at pack-net.co.uk> schrieb: Hi Ishfaq > Look into Busy Lamp Field/Presence > > Here's a starting point: > > http://www.asteriskdocs.org/en/3rd_Edition/asterisk-book-html-chunk/asterisk-DeviceStates-SECT-1.html Thanks a lot, but it does not seems to work... Here my configuration: sip.conf: [general] allowsubscribe=yes subscribecontext = default
2003 Feb 05
1
pxelinux and booting dos
I have got pxelinux booting a DOS ramdisk via the memdisk program from the command line. However I am having a problem getting it to use the configuration file. pxelinux find the configuration directory, pxelinux.cfg and then finds the file, C0A801, and reads the file, but no matter what I put on my "kernel" line, it looks for a kernel named "linux". When I create a sofft
2010 Nov 23
2
pxelinux.cfg/C0A80146 unable to load configuration file
Hi Peter, i am a netboot user of Linux platform. right now, i got a problem. after establishment a new pxe server, the clients boot from the network. and i just do some experiment of reboot on the clients. but i am surprise of the clients booting failure after several cycles. and i got the info of the clients can not download the config file, such as: Trying to load:
2010 Sep 09
2
Invalid or corrupt kernel image
Hi, I am trying to setup my own PXE boot server. I tried several PXE bootable Linux-Distributions. For example if I use the ubuntu netboot image from [1] it works quit well but there are a few other images they do not work in my case e.g.: RIPLinuX [2]. A friend tested this image on his PXE boot server with success. I also checked the download with md5sum. In my case I can see the boot menu [3].
2010 Mar 04
1
PXELINUX output 3.85 vs. 4.00
PXELINUX 3.85 pre13-1-gee43a6e* Copyright (C) 1994-2010 H. Peter Anvin et al !PXE entry point found (we hope) at 9F00:0680 via plan A UNDI code segment at 9F00 len 0AB0 UNDI data segment at 9E00 len 1000 Getting cached packet 01 02 03 My IP address seems to be C0A80168 192.168.1.104 ip=192.168.1.104:192.168.1.99:192.168.1.1:255.255.255.0 TFTP prefix: Trying to load:
2005 Aug 29
1
Different sings for correlations in OLS and TSA
Dear list, I am trying to re-analyse something. I do have two time series, one of which (ts.mar) might help explaining the other (ts.anr). In the original analysis, no-one seems to have cared about the data being time-series and they just did OLS. This yielded a strong positive correlation. I want to know if this correlation is still as strong when the autocorrelations are taken into account.