Conferencing
Conferencing
Hello,
We have installed OTMS version 2.31 and already configured for conferencing service. To manage conferences we are using MyTeamwork Gui client (webclient) not OTC.
OTMS configuration was created via OmniVista 8770 and ACS via OTMS WedAdmin.
The main issue is when conferencing was created and the necessary participants were added (for exampe, 5 participants in conference) invite is formed not to all. Sometimes the system doesnt form a call to one or more participants.
I have make siptace on the OXE side and dont see an invitation from Sip proxy OTMS.
Can any one suggest to me what should I look in additional or do.
Thanks.
We have installed OTMS version 2.31 and already configured for conferencing service. To manage conferences we are using MyTeamwork Gui client (webclient) not OTC.
OTMS configuration was created via OmniVista 8770 and ACS via OTMS WedAdmin.
The main issue is when conferencing was created and the necessary participants were added (for exampe, 5 participants in conference) invite is formed not to all. Sometimes the system doesnt form a call to one or more participants.
I have make siptace on the OXE side and dont see an invitation from Sip proxy OTMS.
Can any one suggest to me what should I look in additional or do.
Thanks.
- cavagnaro
- Alcatel Unleashed Certified Guru
- Posts: 7014
- Joined: 14 Sep 2005 19:45
- Location: Brasil, Porto Alegre
- Contact:
Re: Conferencing
Check dialing rules at teamwork.
Enviado de meu E6633 usando Tapatalk
Enviado de meu E6633 usando Tapatalk
Ignorance is not the problem, the problem is the one who doesn't want to learn
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
Re: Conferencing
You mean DAS rule?
But temwork make calls participants which in the same dialing format.
But temwork make calls participants which in the same dialing format.
- cavagnaro
- Alcatel Unleashed Certified Guru
- Posts: 7014
- Joined: 14 Sep 2005 19:45
- Location: Brasil, Porto Alegre
- Contact:
Re: Conferencing
Yeah, then check TW logs and specially SIP ones.
Just double check your rules.
Can you call them manually via the conference room?
Enviado de meu E6633 usando Tapatalk
Just double check your rules.
Can you call them manually via the conference room?
Enviado de meu E6633 usando Tapatalk
Ignorance is not the problem, the problem is the one who doesn't want to learn
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
Re: Conferencing
Can you call them manually via the conference room?
Yes, from established conference
But temwork make calls participants which in the same dialing format.
For example, 20101,20102,20103,20104 - were invited and 20105 and 20106 didn't
Yes, from established conference
But temwork make calls participants which in the same dialing format.
For example, 20101,20102,20103,20104 - were invited and 20105 and 20106 didn't
- cavagnaro
- Alcatel Unleashed Certified Guru
- Posts: 7014
- Joined: 14 Sep 2005 19:45
- Location: Brasil, Porto Alegre
- Contact:
Re: Conferencing
Ok then check teamwork logs to see if any error raises on logs
Enviado de meu E6633 usando Tapatalk
Enviado de meu E6633 usando Tapatalk
Ignorance is not the problem, the problem is the one who doesn't want to learn
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
Re: Conferencing
More additional information,
1. PBX Numbering Plan 5 digits
2. Directory number begin with 2
3. Prfixes for outgoing calls are 0,00 where 0 - for National, Local Calls and 00 - for International calls
Configured DAS rule,
DAS Rule 1 - s/^\+[xX]?(\d{3,6})$/\1/
DAS Rule 2 - s/^\+(\d{3,6})$/+x\1/
DAS Rule 3 - s/^[\+]?x//
DAS Rule 4 - s/^\+380/00/
DAS Rule 5 - s/^\+M/M/
DAS Rule 6 - s/^\+N/N/
DAS Rule 7 - s/^\+V/V/
DAS Rule 8 - s/^\+/00/
Configured Phone Formatting Rules,
/^\s*\+*[xX]?(\d{3,6})\s*$/
1. PBX Numbering Plan 5 digits
2. Directory number begin with 2
3. Prfixes for outgoing calls are 0,00 where 0 - for National, Local Calls and 00 - for International calls
Configured DAS rule,
DAS Rule 1 - s/^\+[xX]?(\d{3,6})$/\1/
DAS Rule 2 - s/^\+(\d{3,6})$/+x\1/
DAS Rule 3 - s/^[\+]?x//
DAS Rule 4 - s/^\+380/00/
DAS Rule 5 - s/^\+M/M/
DAS Rule 6 - s/^\+N/N/
DAS Rule 7 - s/^\+V/V/
DAS Rule 8 - s/^\+/00/
Configured Phone Formatting Rules,
/^\s*\+*[xX]?(\d{3,6})\s*$/
Re: Conferencing
I got logs (SipServer.log) and when conference was created and started participant 20101 were not invited.
In SipServer.log I saw:
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[INFO] csta: CstaMonitorManager::CreateDeviceMonitor - Monitor for deviceNumber CBA is created, refId=1
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
Information about conference:
patricipants - 20101,20105,20110.
leader - 20111.
In SipServer.log I saw:
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[INFO] csta: CstaMonitorManager::CreateDeviceMonitor - Monitor for deviceNumber CBA is created, refId=1
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
[WARN] csta: CstaMonitorManager::CreateDeviceMonitor - deviceNumber 20101 NOT FOUND
Information about conference:
patricipants - 20101,20105,20110.
leader - 20111.
- cavagnaro
- Alcatel Unleashed Certified Guru
- Posts: 7014
- Joined: 14 Sep 2005 19:45
- Location: Brasil, Porto Alegre
- Contact:
Re: Conferencing
You have a CSTA warning...
Does that extension exists? Do you have enough CSTA licenses?
Enviado de meu E6633 usando Tapatalk
Does that extension exists? Do you have enough CSTA licenses?
Enviado de meu E6633 usando Tapatalk
Ignorance is not the problem, the problem is the one who doesn't want to learn
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
Re: Conferencing
Does that extension exists?
Yes, it's IPTouch 4028 phone
Do you have enough CSTA licenses?
I'll check
Yes, it's IPTouch 4028 phone
Do you have enough CSTA licenses?
I'll check