search for: subaccounts

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

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. One minor detail, we are using ip authentication. When Vitelity changed my account from user based authentication to IP based authentication, they stopped including a user for

...s that are based on your custom structural object classes. You can also specify that a referential integrity overlay is present to skip certain cleanup actions. New modules support dynamic lists and Self Service + Password Self Reset can be secured with a captcha. Unix options are now specific to subaccounts but this also requires to reconfigure the modules. See version specific upgrade instructions. https://www.ldap-account-manager.org/static/doc/manual/ch02s02.html#a_versUpgrade Full changelog: https://www.ldap-account-manager.org/lamcms/changelog Download: https://www.ldap-account-manager.org/...

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... [HVout] type=friend dtmfmode=auto host=64.2.142.93 disallow=all allow=ulaw canreinvite=no trustrpid=yes sendrpid=yes nat=yes context=TestApp On Dec 15, 2014, at 9:32 PM, George Joseph <george.joseph at fairview5.com<mailto:george.joseph at

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). Vitelity doesn?t seem to process it, so they send an OK again. The OK receive, Transmit ACK occurs 4 times. A short while later, Vitelity hangs up

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