You wanted to have the calls go to a "user" during working hours, the AA after
hours. Following the example below, you will create a period that reflects
normal business hours, and have the calls directed to the user (via forwarding,
and picking the time period, at-the-same-time) you want the ca
On 11/13/2008 4:26 PM, Tony Graziano wrote:
> To clarify, the hunt group needs to have the option checked to adhere to user
> forwarding.
>
> The phantom user needs to have a schedule for the time periods, and as an
> example:
>
> Period-afterhours, weekdays 12;00am-8:29am, 4:30pm-11:59pm, weeken
To clarify, the hunt group needs to have the option checked to adhere to user
forwarding.
The phantom user needs to have a schedule for the time periods, and as an
example:
Period-afterhours, weekdays 12;00am-8:29am, 4:30pm-11:59pm, weekends
12:00am-11:59pm, calls are forwarded to autoattenda
The standard way right now is to create a "phanton user" (user account with no
phone). Put that user in a hunt group all alone. Then create a user schedule
and add time periods for that user to handle the call control.
The hunt group needs to have an alias to a did number (if using did) and you
Anybody know of good way to make incoming calls go to one extension from
9-5 then to the autoattendant afterhours?
--
Regards
--
Gerald Drouillard
Technology Architect
Drouillard & Associates, Inc.
http://www.Drouillard.ca
_
Raymund - That would be really great if you could post your findings to the
wiki. I'm a newbie to this, especially OpenSBC, and getting some definitive
information on this setup would be most welcome.
radp1399
On Thu, Nov 13, 2008 at 9:16 AM, Damian Krzeminski <[EMAIL PROTECTED]>wrote:
> Raymun
On Thu, Nov 13, 2008 at 10:07 AM, Raymund Nones <[EMAIL PROTECTED]> wrote:
> hi everyone,
>
> i would like to ask if the sipxecs team could provide a wiki page for
> documenting Sipxecs-OpenSBC setup ? i think there are a lot of people here
> on the list who are interested to document this setup a
On Thu, 2008-11-13 at 12:38 +, Gabor Paller wrote:
> It seems to happen with Cisco 7940 (SIP image, P0S3-08-5-00). It is
> still unconfirmed, seems to happen spuriously and only for a few
> seconds.
There's a way to extract just the messages regarding a single phone:
merge-logs --include-met
Raymund Nones wrote:
> hi everyone,
>
> i would like to ask if the sipxecs team could provide a wiki page for
> documenting Sipxecs-OpenSBC setup ? i think there are a lot of people
> here on the list who are interested to document this setup and are
> willing to contribute to the docu. Currently
hi everyone,
i would like to ask if the sipxecs team could provide a wiki page for
documenting Sipxecs-OpenSBC setup ? i think there are a lot of people here
on the list who are interested to document this setup and are willing to
contribute to the docu. Currently, i'm doing several test scenario
Thanks to everybody who responded.
I think the Exchange 2007 option is the best idea for me (assuming it works!).
It’d also give me a reason to upgrade from 2003.
Scott.
From: Pete Burgess [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2008 12:11 PM
To: sipx-users@list.sipfoundry.org
It seems to happen with Cisco 7940 (SIP image, P0S3-08-5-00). It is
still unconfirmed, seems to happen spuriously and only for a few
seconds.
Regards,
Gabor
-Original Message-
From: Nikolay Kondratyev [mailto:[EMAIL PROTECTED]
Sent: 13 November 2008 12:34
To: Gabor Paller; sipx-users@lis
By the way, what is your endpoint?
Rgds,
Nikolay.
> -Original Message-
> From: Gabor Paller [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 13, 2008 3:31 PM
> To: Nikolay Kondratyev; sipx-users@list.sipfoundry.org
> Subject: RE: [sipx-users] Re-registration problem
>
> Thanks, Nikola
Thanks, Nikolay, that was the problem.
Although in many cases SipX reports back expiration time that is close
to the requested time (e.g. 1800->1703), sometimes it happens that the
expiration time reported back by significantly lower than the requested
value (e.g. 1800->672). The endpoint does not
Hi,
If you really see that your sip endpoint sends register messages every 1800
sec, then I can tell (with high probability) that your endpoint does not
conform to frc 3261 :).
The thing is that, afaik, sipx always "randomly redistributes"
re-registrations: that is when endpoint asks for the regis
Hi,
I am running 3.10.2 and I observed a strange phenomenon about
re-registrations. My endpoint re-registers periodically, with an
expiration value of 1800 seconds. The re-registration is successful,
REGISTER messages and responses are exchanged correctly. Monitoring from
the "Registrations" page
http://sipx-wiki.calivia.com/index.php/Display_SIP_message_flow_using_Sipviewer
>>> "sipxuser sipx" <[EMAIL PROTECTED]> 11/13/08 3:55 AM >>>Hi all, Is there
>>> any utilities can be used to capture and view the sip messages received by
>>> sipx server? Anyone has any comment? Thanks in advance.
hi all ,
I want to know about text-to-speech (tts) that can i use festival engine
with sipx to convert text to speech?As i read in many places about the
festival engine as tts engine and can be integrate with sipx. Is it
possible? Even i dont have enough idea about festival engine that how to run
Hi all,
Is there any utilities can be used to capture and view the sip messages
received by sipx server? Anyone has any comment?
Thanks in advance.
Regards,
Mich.
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sip
19 matches
Mail list logo
