search for: exent

...riting a rd doc, and need to use "#" in a url adress. This would make: \url{http://www.xxxx.org/myfolder/#myanchor} Of course, I suppose this will not work because # is a special character starting a comment line in the rd dialect. I did not found a similar example in "Writing R exentions". I am not sure bout using \dQuote{a quotation}), and use \sQuote and \dQuote correctly. Does anyone know how to get the thing right ? Patrick [[alternative HTML version deleted]]

If my extension is 22, and voice mail access number is 909, then with exten => 909,1,voicemailmain(s22) I can access voice mail 22, without number and password prompt. But, I want that every extension can access its voice mail without number and password. So, when I put exent => 909,1,voicemailmain(${calleridnum}) voicemail want only password. I want to eliminate password too, so when I put exten => 909,1,voicemailmain(s${calleridnum}) this DO NOT work. Voicemail want number and password. Why? Bug?

Hello, Did someone have a solution for a line fax detection for outgoing call For exemple I call number 0123456789 - if it is a fax then redirect to extension A - if it is a line then redirect to exention B whats ia want its somthing like AMD application that i use for the answering machine . http://www.voip-info.org/wiki/view/Asterisk+cmd+AMD search in the wiki give this application : http://www.voip-info.org/wiki/view/NVFaxDetect Did somene use it ? any feed back ? Sorry for the English...

...n't seem to get the tones to be recognized during the background( ) the playback and background files play, but asterisk doesn't do anything when I start pushing keys - I've tried it from softphones and pstn line phones Can anyone tell me what I'm doing wrong? Required contexts Exentions.conf below [from-broadvoice] exten => s,1,Answer exten => s,2,Playback(pbx-candles-welcome) exten => s,3,Background(pbx-candles-mainmenu) exten => 1,1,dial,SIP/101|45|r exten => 1,2,voicemail,1111 exten => 1,3,hangup() exten => 2,1,dial,SIP/101|45|r exten =>...

...but I've come to a wall that I just cant work out how to get past at the moment, so am hoping for some community assistance if possible. Some background: We are running Windows Server 2003 on all of our domain controllers, and are in the middle of migrating to server 2008 R2. We have unix exentions enabled (rfc2307 I believe), and manage all of our uids/shell/home via this. Our linux servers are a mix of RHEL 5.1, 5.4 and 5.5. We were using Samba 3.0.33-3.29.el5_5.1 or equivalent on most of our servers, but we hit a stone wall when trying to get them to co-exist with a domain con...

was wondering if anyone could give us a run through an explanation of the wiki and other examples of connecting to iptel's sip express router using asterisk pbx so i can understand better the call processing .. given the example i work from on john todd's www.loligo.com site ; exten => _3.,1,SetCallerID(${IPTELUSERID}) exten => _3.,2,SetCIDname(${IPTELUSERNAME}) exten =>

...be up to 1MB (depending on user request), we now conditionally vmalloc them. - removed redundant check for same inode. btrfs_extent_same() catches it now and bubbles the error up. - remove some unnecessary printks Changes from RFC to v1: - don''t error on large length value in btrfs exent-same, instead we just dedupe the maximum allowed. That way userspace doesn''t have to worry about an arbitrary length limit. - btrfs_extent_same will now loop over the dedupe range at 1MB increments (for a total of 16MB per request) - cleaned up poorly coded while loop in __extent_...

Hi all - The following 9 patches add more error handling to the btrfs code: - Add btrfs_panic - Catch locking failures in {set,clear}_extent_bit - Push up set_extent_bit errors to callers - Push up lock_extent errors to callers - Push up clear_extent_bit errors to callers - Push up unlock_extent errors to callers - Make pin_down_extent return void - Push up btrfs_pin_extent errors to

Hi all - Here''s my current error handling patchset, against 3.1-rc8. Almost all of this patchset is preparing for actual error handling. Before we start in on that work, I''m trying to reduce the surface we need to worry about. It turns out that there is a ton of code that returns an error code but never actually reports an error. The patchset has grown to 65 patches. 46 of them