Re: [asterisk-users] RE How to break pri DID to multiple SIP Trunks

2010-07-02 Thread Samantha
-users] RE How to break pri DID to multiple SIP Trunks Samantha, Are you using some type of GUI ? If you send all the traffic to a specific context in there you can set a default route to one peer and then set exceptions for the others. For example [from-pri] Exten = _X.,1,Dial(SIP/${ext

[asterisk-users] RE How to break pri DID to multiple SIP Trunks

2010-06-29 Thread Samantha
and sip trunks I can see that all the sip trunks are up I can see the outbound routes are there and also in trunks But it isn't working The call gets answered by the first point xxx.yyy.189.69 and you get an rva of the number you called is not in service Regards Samantha

[asterisk-users] Problem with Hylafax

2010-06-15 Thread Samantha
Hey Guys I have hylafax working about 95% The problem is I have a DID for fax 0742244224 When I receive a fax I see in the log file n 16 02:44:19] VERBOSE[3679] logger.c: -- Executing [0742244...@from-sip-external:1] NoOp(SIP/5060-0a2f7308, Received incoming SIP connection from unknown

[asterisk-users] Re TrixBox

2010-05-09 Thread Samantha
if there are 20 calls on hold in DID 001 and 002 and there is a call on 003, how can we place that to the top of the queue? thanks Samantha -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New

Re: [Asterisk-Users] Re 2 x100p cards H E L P (I have no hair left) Again!

2004-11-15 Thread Samantha (Femtech)
channel =2 r2d2:/etc/asterisk# r2d2:/home/s/samantha# lspci :00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03) :00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] :00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super

[Asterisk-Users] Re Cron

2004-06-27 Thread Samantha (Femtech)
Hi List Is there a cron that I con do to replace this, as the fx0 card doesnt hang up properly phonegc:/home/samantha# asterisk -rAsterisk CVS-05/30/03-17:17:07, Copyright (C) 1999-2001 Linux Support Services, Inc.Written by Mark Spencer [EMAIL PROTECTED