similar to: Cisco 7960 not always receiving incoming calls

I'm trying to add a second extension to my setup. The second device is able to successfully connect to the Asterisk server. I am unable to contact extension 101 from 102 and vise-versa. Also are my context setup logically or is there a better fashion to organize them? My error is at the bottom. Here is the extension.conf [default] ; ; By default we include the demo. In a production system,

I have a Asterisk server setup and I am able to connect to the server using a soft client 'x-lite' and call and leave a message on my second extension 102. I have setup a Vitelity account and add what I believe to be the correct information to my sip.conf and extension.conf. I would like to setup incoming and outgoing calls with voicemail support. I've searched all over but many of the

My latency is kind of high and the voice delay is noticeable. The Asterisk server is on a dedicated host outside of the network. I am performing PAT/NAT using a Cisco router. ns1*CLI> sip show peers Name/username Host Dyn Nat ACL Port Status vitel-outbound/rsreese 64.2.142.22 5060 Unmonitored vitel-inbound/rsreese 64.2.142.116

I would like to create a simple menu that would allow a caller to decide whether they want to leave a message or be forwarded to another number (i.e cell phone). Thanks in advance for any insight. Here's my current extension.conf [general] static=yes writeprotect=yes [globals] [default] exten => 101,1,Dial(SIP/101,20) exten => 101,n,Voicemail(101 at default) ;This automatically

The host I am working with has two accounts from the same DID provider. Incoming calls work correctly and dial the appropriate extensions. This also allows incoming calls to be billed appropriately to the individual DID accounts. Outgoing calls from either extension default to the first DID, i.e. calls from either extension have the same callerID. How can an extension specify separate outgoing

Is there a way to include: _NXXNXXXXXX _NXXXXXX _011. _911 into my current plan:

Hi, all. I'm probably doing Something Dumb(tm), so please feel free to point out whatever I'm missing, no matter how stupid. Anyway, I've got IAX set up to Vitelity. When I try to call my DID, I get: Rejected connect attempt from 64.2.142.19, who was trying to reach '6031234567@' This leads me to my first question -- why doesn't it show a context? (My second is,

I am able to return users and groups using wbinfo -g and -u. Samaba will even allow users to connect that are in our domain. The problem exist while trying to narrow down permissions to a share. [public] comment = Public Stuff path = /home/ public = yes read only = no valid users = @"UFAD\_IFAS-FRE-USERS_autoGS" This does not work. It prompts the end user for a

Evening, Has anyone seen a how-to on getting Asterisk to work with Google Talk and Google Voice? Thanks

Hi, I've been trying to use the FaxGateway application to send T.38 out over Zaptel using asterisk but I don't seem to be having any luck. I'm executing it in the dialplan like: FaxGateway(Zap/g0/[number]) Has anyone had any luck using this thing and can enlighten me on how it's supposed to be used? Thanks.

I'm new to this list, and I apologize if this is an already answered question, but my Google-fu was not strong enough to find the answer if it was. I'm having a problem with DTMF on incoming IAX calls. For the first few seconds of the call (between maybe 1 and 15, it varies from call to call) everything works fine. After that I continue get DTMF_E messages from the remote IAX server

Is anyone else using Vitelity right now and having an issue with a global outage of sorts? Potral/WWW arent accessible and it would appear through monitoring that the outbound is flapipng like mad. The outbound can be rerouted, I know, but inbound is a huge problem right now. [Sep 4 10:26:13] NOTICE[27507]: chan_sip.c:15679 sip_poke_noanswer: Peer 'vitel-outbound' is now UNREACHABLE!

Hi, I have been looking for an example of accomplishing this, but I've been unable to locate something similar to what I'm trying to do. Here's the scenario: Users caller ID is set to their internal extension (200-250). This is set in sip.conf for each user. Each user has a local DID as well (hosted through Vitelity, for example (555)111-2222). The problem is that this extension was

I was thinking about complicating my Voip setup by adding CME. I found this example here: http://www.voip-info.org/wiki/view/Asterisk+Cisco+CallManager+Express+Integration and here: http://www.pasewaldt.com/cme/cme_index.htm Would anyone like to comment on their experiences using CME with Asterisk... I would like one of my Cisco phones to remain SIP connected directly to my Asterisk system. The

Hi, An incoming call is redirected to another number by our asterisk server. In the incoming call the caller name is present but when redirect the call, the end receiver is not able to see the callerid name. The caller id number is visible. our related changes to extensions conf is below. exten => {MY_EXT},14,Set(CALLERID(name)=OH ${CALLERID(name)})<br> exten =>

I have a problem that has developed within about the past 3 months with my backup outgoing SIP provider (I am not sure when this problem started since it involves only my backup provider which is used rarely). The problem is that most (not all) outgoing calls fail during the earliest stages of call setup, specifically after the provider sends back a "407 Proxy Auth Required" response.

Ok Dan, try this... I was able to get this to work behind a NAT and with ip address authentication. [global] type = global debug = yes [transport1] type = transport bind = 0.0.0.0 protocol = udp *local_net=<yourlocalnet I.E. 10.10.10.10/24 <http://10.10.10.10/24>>external_media_address=<your public ip address>external_signaling_address=<your public address>*

On Mon, Dec 15, 2014 at 3:54 PM, Dan Cropp <dan at amtelco.com> wrote: > > Yes, everything is behind the same NAT. > > > > For the application I?m working on, the only endpoint is the endpoint to > Vitelity. > > We use AMI to Originate calls from Asterisk endpoint through Vitelity to > phones. > > After that, we control the call through AMI to perform the

Here's an update... My network admin would not turn off the ALG because it would cause several other problems to other phone systems we have. He looked at the sip trace. What he found is the PJSIP trace showed a different IP address than the older chan_sip so he had me change the aor contact to outbound.vitelity.net At this point, it seems to be working (and this is going through a Cisco

On Mon, Dec 15, 2014 at 7:34 PM, Dan Cropp <dan at amtelco.com> wrote: > > I am not sure if I entered the correct settings for the transport > information. > > For the local_net, I entered my local ip address, but no mask. I will > check with the network admin so he can verify the settings I entered. > > > You need the network and mask. For example if the ip