Displaying 4 results from an estimated 4 matches for "aaf2".
Did you mean:
aaf
2005 Feb 08
0
Codec negotiation problems
...den getting this on certain phone numbers on my system:
Feb 8 22:19:19 NOTICE[1125329728]: channel.c:1683
ast_set_read_format: Unable to find a path from ULAW to G729A
Feb 8 22:19:19 NOTICE[1125329728]: channel.c:1650
ast_set_write_format: Unable to find a path from G729A to ULAW
-- SIP/2101-aaf2 answered SIP/19544342000-375a
-- Attempting native bridge of SIP/19544342000-375a and SIP/2101-aaf2
-- Attempting native bridge of SIP/19544342000-375a and SIP/2101-aaf2
Feb 8 22:19:19 NOTICE[1225991488]: channel.c:1683
ast_set_read_format: Unable to find a path from G729A to ULAW
Feb 8 2...
2003 Sep 10
9
G729
I have come to realize that I don't have to have a g729a license in
order to make use of an ATA-186 or 7460 connecting to another 7460. I
just need to allow the codec in sip.conf.
Now what ramification does that have when I dial out over one of my
analog line (connected to * by a channelbank and a T100P) using my 7460
or ATA-186. The only benefit I am looking for is reduced bandwidth
2019 Mar 01
2
Replication and KCC problems on upgrade
...843,CN=Deleted Objects,CN=Configuration,DC=x-es,DC=com - CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=x-es,DC=com
Not fixing old string component
NOTE: old (due to rename or delete) DN string component for lastKnownParent in object CN=2d38127c-7f95-42f7-aaf2-a42f86d54aab\0ADEL:27e13ab1-9930-4363-9d56-2704f275eed3,CN=Deleted Objects,CN=Configuration,DC=x-es,DC=com - CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=x-es,DC=com
Not fixing old string component
NOTE: old (due to rename or delete) DN string component...
2019 Mar 01
2
Replication and KCC problems on upgrade
Hello all-
I am trying to upgrade a old domain to a newer version. The old DCs are a custom compiled version of Samba, so instead of upgrading the DCs in place, the plan is to upgrade by joining new DCs to the domain, replicating data and then shutting down the old ones after transferring the FSMO roles.
I had the new DC (dc3, version 4.9.4-12) replicating to the other DCs (dc0, versions