Google didn’t turn up many results for this error.
Should I be concerned with this error? Thanks for any help.
[quote][Apr 24 09:08:01] WARNING[7217] translate.c: no samples for ulawtolin
[Apr 24 09:08:16] WARNING[7217] translate.c: no samples for ulawtolin
[Apr 24 09:08:31] WARNING[7217] translate.c: no samples for ulawtolin
[Apr 24 09:08:46] WARNING[7217] translate.c: no samples for ulawtolin
[Apr 24 09:09:01] WARNING[7217] translate.c: no samples for ulawtolin[/quote]
Also, I’m getting these from time to time as well, which I think it due to changes with new asterisk version.
[quote][Apr 24 10:10:00] WARNING[8755] app_queue.c: The device state of this queue member, SIP/105, is still ‘Not in Use’ when it probably should not be! Please check UPGRADE.txt for correct configuration settings.
[Apr 24 10:10:36] WARNING[8846] app_queue.c: The device state of this queue member, SIP/110, is still ‘Not in Use’ when it probably should not be! Please check UPGRADE.txt for correct configuration settings.
[Apr 24 10:20:49] WARNING[8872] app_queue.c: The device state of this queue member, SIP/110, is still ‘Not in Use’ when it probably should not be! Please check UPGRADE.txt for correct configuration settings.
[Apr 24 10:21:01] WARNING[8868] app_queue.c: The device state of this queue member, SIP/105, is still ‘Not in Use’ when it probably should not be! Please check UPGRADE.txt for correct configuration settings.[/quote]
SIP/105 is just one of the phones within my queue.
I have 10 phones/extensions that are static within a queue. And I have a hundred different DID’s that route to that queue as normal.
[quote=“UPGRADE.txt”]* Queues depend on the channel driver reporting the proper state
for each member of the queue. To get proper signalling on
queue members that use the SIP channel driver, you need to
enable a call limit (could be set to a high value so it
is not put into action) and also make sure that both inbound
and outbound calls are accounted for.