search for: acl1

...p [1002] type = aor remove_existing = yes contact = sip:1002 at xxx.xxx.xxx.xxx [1002] type = endpoint context = mycontext transport = transport1 accountcode = 6 dtmf_mode = inband device_state_busy_at = 48 force_rport = no identify_by = username from_user = 1002 disallow = all allow = ulaw acl = acl1 [identify112] type = identify endpoint = 1002 match = 1002 at xxx.xxx.xxx.xxx I setup the registration and the endpoint. [286] type = aor remove_existing = yes contact = sip:286 at xxx.xxx.xxx.xxx qualify_frequency = 60 [auth8] type = auth username = 286 password = yyyyyyyyyyyyyyy [286] type =...

...sting = yes [auth3] type = auth username = 1004 password = SuperSecretProbation [1004] type = endpoint context = IS transport = transport1 auth = auth3 aors = aor3 accountcode = 3 dtmf_mode = rfc4733 device_state_busy_at = 2 force_rport = no moh_passthrough = yes disallow = all allow = ulaw acl = acl1 When a register attempt is received, asterisk outputs... [02/14 12:53:29.870] WARNING[7883] res_pjsip_registrar.c: AOR '1004' not found for endpoint '1004' If I change the aor3 to be 1004, everything works. As in [aor3] becomes [1004] and in the endpoint change aors = aor3 to be...

...p [1002] type = aor remove_existing = yes contact = sip:1002 at xxx.xxx.xxx.xxx [1002] type = endpoint context = mycontext transport = transport1 accountcode = 6 dtmf_mode = inband device_state_busy_at = 48 force_rport = no identify_by = username from_user = 1002 disallow = all allow = ulaw acl = acl1 [identify112] type = identify endpoint = 1002 match = 1002 at xxx.xxx.xxx.xxx<mailto:1002 at xxx.xxx.xxx.xxx> Check this first... identify112 probably failed to load because the match parameter can only take an ip address plus an optional netmask, or a hostname. The '1002@' is in...

...aor remove_existing = yes contact = sip:1002 at xxx.xxx.xxx.xxx [1002] type = endpoint context = mycontext transport = transport1 accountcode = 6 dtmf_mode = inband device_state_busy_at = 48 force_rport = no identify_by = username from_user = 1002 disallow = all allow = ulaw acl = acl1 [identify112] type = identify endpoint = 1002 match = 1002 at xxx.xxx.xxx.xxx<mailto:1002 at xxx.xxx.xxx.xxx> Check this first... identify112 probably failed to load because the match parameter can only take an ip address plus an optional netmask, or a hostname. The '1002@...

On btrfs, do the following ------------------ # su user1 # cd btrfs-part/ # touch aaa # getfacl aaa # file: aaa # owner: user1 # group: user1 user::rw- group::rw- other::r-- # su user2 # cd btrfs-part/ # setfacl -m u::rwx aaa # getfacl aaa # file: aaa # owner: user1 # group: user1 user::rwx <- successed to setfacl group::rw- other::r-- ------------------ but we

...mat to g729 when disallow = all and allow = ulaw are the endpoint settings? [121] type = endpoint context = IS transport = transport1 aors = 121 accountcode = 2 dtmf_mode = inband device_state_busy_at = 96 force_rport = no identify_by = username,ip disallow = all allow = ulaw from_user = 121 acl = acl1 [10/03 11:29:34.240] DEBUG[21414][C-00000226] chan_pjsip.c: Oooh, got a frame with format of g729 on channel 'PJSIP/121-000001d2' when we're sending 'ulaw', switching to match INVITE sip:2197 at XXX.XXX.XXX.XXX:5060 SIP/2.0 Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;branch=z9hG4bK...

...xt = IS > > transport = transport1 > > auth = auth3 > > aors = aor3 > > accountcode = 3 > > dtmf_mode = rfc4733 > > device_state_busy_at = 2 > > force_rport = no > > moh_passthrough = yes > > disallow = all > > allow = ulaw > > acl = acl1 > > > > > > When a register attempt is received, asterisk outputs… > > [02/14 12:53:29.870] WARNING[7883] res_pjsip_registrar.c: AOR '1004' not > found for endpoint '1004' > > > > If I change the aor3 to be 1004, everything works. As in [aor3]...

Thank you Joshua. I tried setting the from_domain for the endpoint, but it still sends the internal ip address for the INVITE's From field [acl1] type = acl deny = 0.0.0.0/0.0.0.0 permit = variousaddress permit = bluipaddress [transport1] type = transport bind = 0.0.0.0 protocol = udp [BLUIPIN] type = aor remove_existing = yes contact = sip:bluipaddress [auth7] type = auth username = didassignedbybluip password = password [didassignedb...

I am trying to configure a connection to BluIP. I am able to make incoming calls work. However outgoing calls are not working. For the Outbound Registration, I noticed the contact field is always the internal IP address of my pc instead of mycompany dot com I can Originate (using AMI) to my Vitelity trunk (IP based authentication). However, when I Originate to my BluIP, it is being rejected.