innovaphone wiki - User contributions [en]

Reference9 talk:Concept myPBX

2011-12-14T13:44:36Z

Passvoip: New page: Two questions: 1. Will the HTTP request based interface be (more or less) stable in the future, i.e. can we use it for own integration purposes? 2. Are there any limits regarding the num...

Two questions:

1. Will the HTTP request based interface be (more or less) stable in the future, i.e. can we use it for own integration purposes?

2. Are there any limits regarding the number of parallel client sessions or can every configured user run at least one myPBX client?

Thanks!

Howto talk:Create Conference Facility with Notification

2011-11-21T19:46:10Z

Passvoip: New page: The solution does not work anymore after upgrading to V9 (hf5). The user always receives "no channel available". Any idea?

The solution does not work anymore after upgrading to V9 (hf5). The user always receives "no channel available". Any idea?

Howto:Create Conference Facility with Notification

2010-07-04T15:59:05Z

Passvoip: /* More Information */

==Applies To==
This information applies to

* IP 3000, V4
* IP 400, V4
* IP 21, V4
Build 01-4001 and later.



==More Information==
This article describes how to provide a number of conference rooms with access codes and notification tones on entering a room.
===SolutionDetails===
The conference rooms are represented by the needed number of Bc Conference objects. A Waiting Queue servs as central entry point to the different rooms. Whenever a call connects to the Waiting Queue, the user will be asked for a conference code. If the user enters a valid conference code, he/she will be connected to the respective conference room and every user within the room will hear a notification.

===Installation===
1. Create one Bc Conference object per conference room.
Assign a base number (967 in our case) plus an one digit room number.

[[Image:telco01.png]]

Assign the room number to Conference Id.

[[Image:telco02.png]]

Repeat these steps for all conference rooms wanted. Be sure to assign a unique room number/Conference Id to each conference room.

2. Create an individual group per Bc Conference object (i.e per conference room) and make the Bc Conference object active member of its group

3. Create an User object and name it for example "TelcoNotification". Make this user object non-active member of each group created before.

4. Go to Gateway->Interfaces->HTTP and register the HTTP i/f at the gatekeeper address 127.0.0.1 using the name of the User object ("TelcoNotification" in our case)

[[Image:telco03.png]]

5. Provide an appropriate sound file (just a beep or what ever you want) on the CF card or any other location accessible via WebDav.

6. Go to Gateway-Routes and edit the route RWEB:TelcoNotification->HTTP:TelcoNotification
Enter the URL of your sound file in "Add UUI". Be sure to provide the parameters "coder" and "disc" with the proper values (disc needs to be true!)

[[Image:telco04.png]]

7. Finally, create a Waiting Queue object as central entry point for all conference rooms:

[[Image:telco05.png]]

Set the URL for 1st Announcement to a sound file of your choice (e.g. "Pls. enter your conference code")

[[Image:telco06.png]]

Use the DTMF maps to create conference codes and assign the respective rooms (i.e. the names of the Bc Conference objects created before)

[[Image:telco07.png]]

===Known Problems===
If the user enters an invalid conference code, simply the announcement to enter a code will be repeated.

It's (currently) not possible to notify an entering user about the number of already existing participants.


[[Category:Howto|{{PAGENAME}}]]

Howto:Create Conference Facility with Notification

2010-07-04T15:58:24Z

Passvoip: /* Known Problems */

==Applies To==
This information applies to

* IP 3000, V4
* IP 400, V4
* IP 21, V4
Build 01-4001 and later.



==More Information==
This article shows how to provide a number of conference rooms with access codes and notification tones on entering a room.
===SolutionDetails===
The conference rooms are represented by the needed number of Bc Conference objects. A Waiting Queue servs as central entry point to the different rooms. Whenever a call connects to the Waiting Queue, the user will be asked for a conference code. If the user enters a valid conference code, he/she will be connected to the respective conference room and every user within the room will hear a notification.

===Installation===
1. Create one Bc Conference object per conference room.
Assign a base number (967 in our case) plus an one digit room number.

[[Image:telco01.png]]

Assign the room number to Conference Id.

[[Image:telco02.png]]

Repeat these steps for all conference rooms wanted. Be sure to assign a unique room number/Conference Id to each conference room.

2. Create an individual group per Bc Conference object (i.e per conference room) and make the Bc Conference object active member of its group

3. Create an User object and name it for example "TelcoNotification". Make this user object non-active member of each group created before.

4. Go to Gateway->Interfaces->HTTP and register the HTTP i/f at the gatekeeper address 127.0.0.1 using the name of the User object ("TelcoNotification" in our case)

[[Image:telco03.png]]

5. Provide an appropriate sound file (just a beep or what ever you want) on the CF card or any other location accessible via WebDav.

6. Go to Gateway-Routes and edit the route RWEB:TelcoNotification->HTTP:TelcoNotification
Enter the URL of your sound file in "Add UUI". Be sure to provide the parameters "coder" and "disc" with the proper values (disc needs to be true!)

[[Image:telco04.png]]

7. Finally, create a Waiting Queue object as central entry point for all conference rooms:

[[Image:telco05.png]]

Set the URL for 1st Announcement to a sound file of your choice (e.g. "Pls. enter your conference code")

[[Image:telco06.png]]

Use the DTMF maps to create conference codes and assign the respective rooms (i.e. the names of the Bc Conference objects created before)

[[Image:telco07.png]]

===Known Problems===
If the user enters an invalid conference code, simply the announcement to enter a code will be repeated.

It's (currently) not possible to notify an entering user about the number of already existing participants.


[[Category:Howto|{{PAGENAME}}]]

File:Telco07.png

2010-07-04T15:52:16Z

Passvoip:

File:Telco06.png

2010-07-04T15:51:57Z

Passvoip:

File:Telco05.png

2010-07-04T15:51:40Z

Passvoip:

File:Telco04.png

2010-07-04T15:51:16Z

Passvoip:

File:Telco03.png

2010-07-04T15:50:57Z

Passvoip:

Howto:Create Conference Facility with Notification

2010-07-04T15:50:44Z

Passvoip: /* Installation */

==Applies To==
This information applies to

* IP 3000, V4
* IP 400, V4
* IP 21, V4
Build 01-4001 and later.



==More Information==
This article shows how to provide a number of conference rooms with access codes and notification tones on entering a room.
===SolutionDetails===
The conference rooms are represented by the needed number of Bc Conference objects. A Waiting Queue servs as central entry point to the different rooms. Whenever a call connects to the Waiting Queue, the user will be asked for a conference code. If the user enters a valid conference code, he/she will be connected to the respective conference room and every user within the room will hear a notification.

===Installation===
1. Create one Bc Conference object per conference room.
Assign a base number (967 in our case) plus an one digit room number.

[[Image:telco01.png]]

Assign the room number to Conference Id.

[[Image:telco02.png]]

Repeat these steps for all conference rooms wanted. Be sure to assign a unique room number/Conference Id to each conference room.

2. Create an individual group per Bc Conference object (i.e per conference room) and make the Bc Conference object active member of its group

3. Create an User object and name it for example "TelcoNotification". Make this user object non-active member of each group created before.

4. Go to Gateway->Interfaces->HTTP and register the HTTP i/f at the gatekeeper address 127.0.0.1 using the name of the User object ("TelcoNotification" in our case)

[[Image:telco03.png]]

5. Provide an appropriate sound file (just a beep or what ever you want) on the CF card or any other location accessible via WebDav.

6. Go to Gateway-Routes and edit the route RWEB:TelcoNotification->HTTP:TelcoNotification
Enter the URL of your sound file in "Add UUI". Be sure to provide the parameters "coder" and "disc" with the proper values (disc needs to be true!)

[[Image:telco04.png]]

7. Finally, create a Waiting Queue object as central entry point for all conference rooms:

[[Image:telco05.png]]

Set the URL for 1st Announcement to a sound file of your choice (e.g. "Pls. enter your conference code")

[[Image:telco06.png]]

Use the DTMF maps to create conference codes and assign the respective rooms (i.e. the names of the Bc Conference objects created before)

[[Image:telco07.png]]

===Known Problems===



[[Category:Howto|{{PAGENAME}}]]

File:Telco02.png

2010-07-04T15:49:20Z

Passvoip:

Howto:Create Conference Facility with Notification

2010-07-04T15:48:57Z

Passvoip: /* Installation */

==Applies To==
This information applies to

* IP 3000, V4
* IP 400, V4
* IP 21, V4
Build 01-4001 and later.



==More Information==
This article shows how to provide a number of conference rooms with access codes and notification tones on entering a room.
===SolutionDetails===
The conference rooms are represented by the needed number of Bc Conference objects. A Waiting Queue servs as central entry point to the different rooms. Whenever a call connects to the Waiting Queue, the user will be asked for a conference code. If the user enters a valid conference code, he/she will be connected to the respective conference room and every user within the room will hear a notification.

===Installation===
1. Create one Bc Conference object per conference room.
Assign a base number (967 in our case) plus an one digit room number.
[[Image:telco01.png]]
Assign the room number to Conference Id.
[[Image:telco02.png]]
Repeat these steps for all conference rooms wanted. Be sure to assign a unique room number/Conference Id to each conference room.

2. Create an individual group per Bc Conference object (i.e per conference room) and make the Bc Conference object active member of its group

3. Create an User object and name it for example "TelcoNotification". Make this user object non-active member of each group created before.

4. Go to Gateway->Interfaces->HTTP and register the HTTP i/f at the gatekeeper address 127.0.0.1 using the name of the User object ("TelcoNotification" in our case)
[[Image:telco03.png]]

5. Provide an appropriate sound file (just a beep or what ever you want) on the CF card or any other location accessible via WebDav.

6. Go to Gateway-Routes and edit the route RWEB:TelcoNotification->HTTP:TelcoNotification
Enter the URL of your sound file in "Add UUI". Be sure to provide the parameters "coder" and "disc" with the proper values (disc needs to be true!)
[[Image:telco04.png]]

7. Finally, create a Waiting Queue object as central entry point for all conference rooms:
[[Image:telco05.png]]
Set the URL for 1st Announcement to a sound file of your choice (e.g. "Pls. enter your conference code")
[[Image:telco06.png]]
Use the DTMF maps to create conference codes and assign the respective rooms (i.e. the names of the Bc Conference objects created before)
[[Image:telco07.png]]

===Known Problems===



[[Category:Howto|{{PAGENAME}}]]

File:Telco01.png

2010-07-04T15:48:10Z

Passvoip:

Howto:Create Conference Facility with Notification

2010-07-04T15:47:17Z

Passvoip: /* Installation */

==Applies To==
This information applies to

* IP 3000, V4
* IP 400, V4
* IP 21, V4
Build 01-4001 and later.



==More Information==
This article shows how to provide a number of conference rooms with access codes and notification tones on entering a room.
===SolutionDetails===
The conference rooms are represented by the needed number of Bc Conference objects. A Waiting Queue servs as central entry point to the different rooms. Whenever a call connects to the Waiting Queue, the user will be asked for a conference code. If the user enters a valid conference code, he/she will be connected to the respective conference room and every user within the room will hear a notification.

===Installation===
1. Create one Bc Conference object per conference room.
Assign a base number (967 in our case) plus an one digit room number.
[[Image:conf01.jpg]]
Assign the room number to Conference Id.
[[Image:conf02.jpg]]
Repeat these steps for all conference rooms wanted. Be sure to assign a unique room number/Conference Id to each conference room.

2. Create an individual group per Bc Conference object (i.e per conference room) and make the Bc Conference object active member of its group

3. Create an User object and name it for example "TelcoNotification". Make this user object non-active member of each group created before.

4. Go to Gateway->Interfaces->HTTP and register the HTTP i/f at the gatekeeper address 127.0.0.1 using the name of the User object ("TelcoNotification" in our case)
[[Image:telco03.png]]

5. Provide an appropriate sound file (just a beep or what ever you want) on the CF card or any other location accessible via WebDav.

6. Go to Gateway-Routes and edit the route RWEB:TelcoNotification->HTTP:TelcoNotification
Enter the URL of your sound file in "Add UUI". Be sure to provide the parameters "coder" and "disc" with the proper values (disc needs to be true!)
[[Image:telco04.png]]

7. Finally, create a Waiting Queue object as central entry point for all conference rooms:
[[Image:telco05.png]]
Set the URL for 1st Announcement to a sound file of your choice (e.g. "Pls. enter your conference code")
[[Image:telco06.png]]
Use the DTMF maps to create conference codes and assign the respective rooms (i.e. the names of the Bc Conference objects created before)
[[Image:telco07.png]]

===Known Problems===



[[Category:Howto|{{PAGENAME}}]]

Howto:Create Conference Facility with Notification

2010-07-04T15:45:13Z

Passvoip: /* SolutionDetails */

==Applies To==
This information applies to

* IP 3000, V4
* IP 400, V4
* IP 21, V4
Build 01-4001 and later.



==More Information==
This article shows how to provide a number of conference rooms with access codes and notification tones on entering a room.
===SolutionDetails===
The conference rooms are represented by the needed number of Bc Conference objects. A Waiting Queue servs as central entry point to the different rooms. Whenever a call connects to the Waiting Queue, the user will be asked for a conference code. If the user enters a valid conference code, he/she will be connected to the respective conference room and every user within the room will hear a notification.

===Installation===
1. Create one Bc Conference object per conference room.
Assign a base number (967 in our case) plus an one digit room number.
[[Image:conf01.jpg]]
Assign the room number to Conference Id.
[[Image:conf02.jpg]]
Repeat these steps for all conference rooms wanted. Be sure to assign a unique room number/Conference Id to each conference room.

2. Create an individual group per Bc Conference object (i.e per conference room) and make the Bc Conference object active member of its group

3. Create an User object and name it for example "TelcoNotification". Make this user object non-active member of each group created before.

4. Go to Gateway->Interfaces->HTTP and register the HTTP i/f at the gatekeeper address 127.0.0.1 using the name of the User object ("TelcoNotification" in our case)
[[Image:telco03.png]]

5. Provide an appropriate sound file (just a beep or what ever you want) on the CF card or any other location accessible via WebDav.

6. Go to Gateway-Routes and edit the route RWEB:TelcoNotification->HTTP:TelcoNotification
Enter the URL of your sound file in "Add UUI". Be sure to provide the parameters "coder" and "disc" with the proper values (disc needs to be true!)

7. Finally, create a Waiting Queue object as central entry point for all conference rooms:
[[Image:telco05.png]]
Set the URL for 1st Announcement to a sound file of your choice (e.g. "Pls. enter your conference code")
Use the DTMF maps to create conference codes and assign the respective rooms (i.e. the names of the Bc Conference objects created before)

===Known Problems===



[[Category:Howto|{{PAGENAME}}]]

Howto:Create Conference Facility with Notification

2010-07-04T15:39:49Z

Passvoip: /* Installation */

==Applies To==
This information applies to

* IP 3000, V4
* IP 400, V4
* IP 21, V4
Build 01-4001 and later.



==More Information==
This article shows how to provide a number of conference rooms with access codes and notification tones on entering a room.
===SolutionDetails===

===Installation===
1. Create one Bc Conference object per conference room.
Assign a base number (967 in our case) plus an one digit room number.
[[Image:conf01.jpg]]
Assign the room number to Conference Id.
[[Image:conf02.jpg]]
Repeat these steps for all conference rooms wanted. Be sure to assign a unique room number/Conference Id to each conference room.

2. Create an individual group per Bc Conference object (i.e per conference room) and make the Bc Conference object active member of its group

3. Create an User object and name it for example "TelcoNotification". Make this user object non-active member of each group created before.

4. Go to Gateway->Interfaces->HTTP and register the HTTP i/f at the gatekeeper address 127.0.0.1 using the name of the User object ("TelcoNotification" in our case)
[[Image:telco03.png]]

5. Provide an appropriate sound file (just a beep or what ever you want) on the CF card or any other location accessible via WebDav.

6. Go to Gateway-Routes and edit the route RWEB:TelcoNotification->HTTP:TelcoNotification
Enter the URL of your sound file in "Add UUI". Be sure to provide the parameters "coder" and "disc" with the proper values (disc needs to be true!)

7. Finally, create a Waiting Queue object as central entry point for all conference rooms:
[[Image:telco05.png]]
Set the URL for 1st Announcement to a sound file of your choice (e.g. "Pls. enter your conference code")
Use the DTMF maps to create conference codes and assign the respective rooms (i.e. the names of the Bc Conference objects created before)

===Known Problems===



[[Category:Howto|{{PAGENAME}}]]

Howto:Create Conference Facility with Notification

2010-07-04T15:27:56Z

Passvoip: New page: ==Applies To== This information applies to * IP 3000, V4 * IP 400, V4 * IP 21, V4 Build 01-4001 and later. <!-- Keywords: enter keywords, foreign translations and/or synoyms not appearin...

Howto talk:Create Conference facility

2010-04-25T13:51:05Z

Passvoip:

I think, this is a nice feature.
But there is one disadvantage: Everyone inside the company can join the conference.
Is there a possibility to join the conference by enter a pin or i start a confernce and only the persons i call are in the conference?--[[User:Martin|Martin]] 14:43, 25 September 2008 (CEST)

Yet some other disadvantages:
- no notification when someone enters or leaves the conference. Any idea how to provide this (i.e. play a sound)?
- no feedback if there's still someone in the conference or not. Even the call info on the SOAP interface can't be used to determine the number of connected calls because the conference room number is not available. Any idea?

Thanks!
--[[User:Passvoip|Passvoip]] 15:51, 25 April 2010 (CEST)

Howto talk:Create Conference facility

2010-04-25T13:49:54Z

Passvoip:

Reference8 talk:Administration/PBX/Objects/Waiting Queue

2010-01-14T14:53:37Z

Passvoip:

Reference8 talk:Administration/PBX/Objects/Waiting Queue

2010-01-12T20:26:21Z

Passvoip:

Hi,

is it possible to have an voicemail object as queue operator (i.e. to make the queue sending calls to a vm script instead of to a phone)?

I added a voicemail object directly to the prim. group of the queue, but it never will be called.
I also tried to use an user object within the prim. group of the queue and a cfu to the voicemail object. Although "CFU disables Operator" is _not_ checked, the vm script will also never be called.
And even a fork setting on the user object will be ignored...

Is this behaviour intended? Any other idea to accomplish what I would like to do?

Thanks!

Jörg Wolf

Yes it is intended, a waiting queue cant be an operator. ''CFU disables operator'' simply says that an operator is not called if there is a CFU on it (which is normally the case).
Nevertheless, your scenario is easy to fix. Look at the [[Howto:Mobile Extension]] to get the idea (you need a user object that routes calls to the waiting queue).

Thanks for the hint, but I don't see how to adapt it to my scenario!? I think my scenario is quite the opposite: incoming calls should be enqueued into a waiting queue. The waiting queue should deliver the longest waiting call to a voicexml script (via voicemail object) which is the only "operator" in the queue's group and will distribute the call in a way similar to the sample [[Howto:Simple ACD with Voicemail XML Script]].

Any further help will be appreciated!
Thanx!
Jörg

Reference8 talk:Administration/PBX/Objects/Waiting Queue

2010-01-09T20:19:36Z

Passvoip: New page: Hi, is it possible to have an voicemail object as queue operator (i.e. to make the queue sending calls to a vm script instead of to a phone)? I added a voicemail object directly to the p...

Howto talk:Simple Linear ACD with Voicemail XML Script

2009-10-31T20:21:33Z

Passvoip: New page: Hi, I noticed that the remote leg of forwarded calls (pbx-fwd) is '''not destroyed''' if the local party (phone, not voicemail) hangs up first! This seems to be a general bug. Any idea?...

Hi,

I noticed that the remote leg of forwarded calls (pbx-fwd) is '''not destroyed''' if the local party (phone, not voicemail) hangs up first!

This seems to be a general bug.

Any idea?

Thx
Jörg