similar to: Vitelity Asterisk configuration help

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've searched around and found a few similar situations where the phone will call out when using a Asterisk server but not receive inbound calls. My issue is a little stranger. If I call out from the phone then the phone will receive the next inbound call. The phone will not receive another inbound call until a call out again from it first. Any ideas? I am using SIP and am using the latest

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

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

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

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,

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

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

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

On Mon, Dec 15, 2014 at 3:33 PM, Dan Cropp <dan at amtelco.com> wrote: > > Hi George, > > > > Thank you for looking into this. > > This is behind a nat? > > > Just to be clear...both the pbx and local endpoints are behind the same NAT? > [global] > > type = global > > debug = yes > > > > [transport1] > > type = transport

Not sure why, but Vitelity changed the settings to IP based authentication on me. Here's the new sip.conf settings they sent me. type=friend dtmfmode=auto host=64.2.142.93 allow=all nat=yes canreinvite=no trustrpid=yes sendrpid=yes When I use these settings to originate calls using the sip.conf they sent me, everything works. Action: Originate ActionID: S8 Channel:

On Mon, Dec 15, 2014 at 9:48 PM, Dan Cropp <dan at amtelco.com> wrote: > > Thanks George. > > I will correct my local_net in the morning. > > Vitelity chan_sip settings I have working, do not have a fromuser. > sip.conf settings... > > I think you can actually specify anything, it just has to be populated with something other than a sub-account username. >

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

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 have a Vitelity DID which generally works, but calls from a particular caller do not reach it. Vitelity has thus far disavowed any responsibility for working through this problem. I recognize that some action might be required by another provider which is outside Vitelity's control, but it seems that they should at least be trying to help resolve the problem by helping me determine

Dan Cropp wrote: > I corrected my local_net setting (based on advice from network admin). > > I have tried several different values for the from_user and still have > the same problem. > > Asterisk receives the OK from Vitelity. > > Asterisk sends the ACK (without a Contact header). A Contact header is not required to be in the ACK. > > Vitelity doesn?t seem to

Any vitelity customers with pbxinaflash boxes? I'm able to call in-house, but failing to make outbound calls. My assigned server at vitelity is not reachable. I can ping to my ISP OK. Any help appreciated. Such as actually how to make email contact with support at vitelity. They're not responding. Thanks, Tom

On Mon, Dec 15, 2014 at 2:08 PM, Dan Cropp <dan at amtelco.com> wrote: > > Today, I tried the same behavior on Asterisk 13.1.0 and Asterisk 12.2.0. > > > > Same problem is happening with both of them. > > > > Could this be caused by PJPROJECT 2.3? > > > > Anyone have any suggestions for what I can try? > > > > My boss is giving me until

On 8/9/16 12:40 PM, Matt Fredrickson wrote: > On Mon, Aug 8, 2016 at 9:25 AM, Tammy Firefly <tammy-lists at wiztech.biz> wrote: >> Hi All, >> >> We have asterisk 11.23 running sip to vitelity and from there IAX trunks >> split off to where they need to go. We are having a problem getting >> chan_sip to quit ignoring re-invites from Vitelity. Our side ends