I wanted to quickly export several months of calls from the CDR to a .csv via
the 'Download' link on the Historic tab of the CDR screen (to run some quick
analysis requested by a user). The file only outputs the first 25,000 records.
Version: 4.4.0-2012-10-19
Nathaniel Watkins
CIO - DoTCom
G
What tony said. Set DND on the line on the executive phone - it simply
turns off the ringer on it, or set it to a ring tone that is silent. Create
a secondary extension that is in an odd range, and then create a dial plan
that excludes that range, and a dial plan that includes it. Assigned the
By the same token you might be able to craft a rule (dial plan) to redirect
or null process that destination. It would be simpler to turn the ringer
off and simply ignore the calls and add the line to an admin assistant who
would field answering those calls.
--
LAN/Telephony/Security and Control
Hi Ali,
On Thu, Jan 3, 2013 at 12:08 PM, Ali Ardestani wrote:
> Hi all,
>
> Is there a way to implement extensions that not all other extensions can
> call (VIP extensions)?
>
I don't think this is possible, if an extension is registered it can be
called. You can use the /etc/sipxpbx/cidrul
You should also take a look as to why proxy thinks its external port is
55060. sipx only supports synchronized firewall ports.
--
INVITE sip:11404@192.168.1.110:2048;line=5nrfoelc SIP/2.0
Record-Route:
Call-Id: bee104006623-50e810fd-729c9139-3b5e9008-8c3a119@127.0.0.1-0
Cseq: 210
Two colleagues just tried that and it work!! Thanks again Tony!!
On Mon, Jan 7, 2013 at 3:39 PM, Tony Graziano
wrote:
> You should disable gruu on the snom.
> On Jan 7, 2013 10:24 AM, "Sven Evensen" wrote:
>
>> Thanks for a few good tips Tony. The outbound calls work fine, it is only
>> the inbo
You should disable gruu on the snom.
On Jan 7, 2013 10:24 AM, "Sven Evensen" wrote:
> Thanks for a few good tips Tony. The outbound calls work fine, it is only
> the inbound call which fails. It is because sipxProxy is relaying ACK to
> the internal IP of the phone, wrong of course. I have looked
Thanks for a few good tips Tony. The outbound calls work fine, it is only
the inbound call which fails. It is because sipxProxy is relaying ACK to
the internal IP of the phone, wrong of course. I have looked at the
REGISTER and the only field I can see which differs from the soft phone
(which works
it might be more pertinent to post a sanitized config of the phone. As
I recall the snom's dont configure "the same" as a polycom (SRV
records, etc.). I also know there is a patch just committed for Snom
on 4.6, so you might ask the devs (Domenico authored the patch) about
what was changed, and why
thanks
On Mon, Jan 7, 2013 at 11:49 AM, George Niculae wrote:
> On Thu, Dec 13, 2012 at 2:57 PM, Douglas Hubler wrote:
>
>> indeed, quality patch! nice!
>>
>>
> Code committed in master:
> https://github.com/dhubler/sipxecs/commit/b28afd4426e0c2f139f62f43b1a8c0db1a3bd488
>
> Thanks!
> George
On Thu, Dec 13, 2012 at 2:57 PM, Douglas Hubler wrote:
> indeed, quality patch! nice!
>
>
Code committed in master:
https://github.com/dhubler/sipxecs/commit/b28afd4426e0c2f139f62f43b1a8c0db1a3bd488
Thanks!
George
___
sipx-users mailing list
sipx-users
On Sat, Jan 5, 2013 at 6:35 AM, Joegen Baclor wrote:
> I think 404 is the desired behavior and no change is needed on the
> config side. A non existing resource list because there is no current
> member of that list is the logical consequence. However, if openfire
> subscribe client is not ch
12 matches
Mail list logo
