similar to: Asterisk & Vitelity Invite issues

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

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

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

Vitelity seems to be offline to both IP and voice traffic. Is there any place to find out what their status is? Roger Marquis

Hello, as a variation of our issues with Adhearsion calls dropping when an INVITE comes in for a bridged call, I now have a new issue to contend with. Our call is in an AsyncAGI application, and has been bridged to another channel. The provider that supplies the DID sends a polling reINVITE every 15 minutes (it's a documented Metaswitch behavior amongst others). The reINVITE is seen as a new

On Mon, Dec 15, 2014 at 3:34 AM, Recursive <lists at binarus.de> wrote: > <snip> >> For asterisk 1.6 & 1.8 you would need to set 'canreinvite=no', I don't know what Asterisk 13 will do with this setting. >> > I suspect Asterisk 13 will just ignore it. To make things worse, there seems to be a configuration directive named reinvite (not a typo); I

Just emailing the list to see if anyone out there has used Vitelity? If so what has been your experience with service, support etc? Thanks Curt

Hello Anyone here uses Vitelity as voip provider ? Their pplans looks good but i need some feedback from existing customers if any here . -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070324/8bb0be73/attachment.htm

Hello, at first, thanks for helping! In the meantime, I have done a lot of research and trial and error, and I could solve that specific problem. Obviously, the dialplan application "Answer" was playing a key role here. My original dialplan snippet (which produced that problem) was: exten => _00., 1, NoOp() same => n, Set(FAXOPT(gateway)=yes) same => n,

Hi All- ? I have successfully routed calls into our asterisk system from several DID providers in the USA, but for some reason I'm having a problem getting Vitelity to work. ? We are using the IAX protocol, and the symptom is that only about 50% of the calls terminate properly into my asterisk system - the rest get a busy signal.? The ones that do not come in don't show up at all on

Hi All, We are using asterisk 16.5 and having an issue with the first re-invite after the call has been established. We can see the call gets up and you see in the logs the bridge type has changed and after that a re-invite is triggered. Is there any possibility to deactivate this kind of reInvite? We have some race conditions while have multiple asterisk in the call flow and the different

I appreciate your report (below), but it's a strange and disturbing coincidence for me. DTMF out through Vitelity was not working for me until 1-2 days ago when I changed it from rfc2833 to inband! Maybe I just missed the change date and I should change it back? ---- Date: Tue, 22 Jul 2008 12:23:39 -0400 From: "Mark G. Thomas" <Mark at Misty.com> Subject: [asterisk-users]

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,

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,

Hi, with canreinvite=no and directmedia=no I and getting the message in the logs for all calls "switching from simple_bridge technology to native_rtp" -- Executing [102 at mkg:1] Dial("SIP/101-00000017", "SIP/102") in new stack == Using SIP RTP CoS mark 5 -- Called SIP/102 -- SIP/102-00000018 is ringing -- SIP/102-00000018 answered SIP/101-00000017

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>*

Hi, Last week my outbound (dtmfmode=inband) DTMF via Vitelity started acting more weird than usual, and for outbound calls, incoming DTMF tones would consistenly get stuck, breaking a call screen macro I had set up. I checked "sip show peer" and saw that Vitelity for inbound was now reporting "DTMFmode : rfc2833" (it didn't used to), so switched my ountbound dtmfmode to

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