[Home]

Summary:ASTERISK-17170: Problem with unistim on Asterisk 1.8.1.1
Reporter:Teq (tequ)Labels:
Date Opened:2010-12-28 04:33:24.000-0600Date Closed:2011-01-19 10:12:15.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_unistim
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have a problem with unistim channel. I don't hear anything during the call.
In addition, any calls to nortel phone causes asterisk crash.

*CLI> [Dec 28 11:12:25] WARNING[15177]: res_rtp_asterisk.c:422 create_new_socket: Unable to allocate RTP socket: Address family not supported by protocol
[Dec 28 11:12:25] WARNING[15177]: chan_unistim.c:2073 start_rtp: Unable to create RTP session: Address family not supported by protocol binaddr=10.0.0.21
   -- Starting switch on '999@2002-0' to 123456
   -- Executing [123456@incoming:1] Answer("999@2002-0", "") in new stack
[Dec 28 11:12:25] WARNING[15187]: res_rtp_asterisk.c:422 create_new_socket: Unable to allocate RTP socket: Address family not supported by protocol
[Dec 28 11:12:25] WARNING[15187]: chan_unistim.c:2073 start_rtp: Unable to create RTP session: Address family not supported by protocol binaddr=10.0.0.21
   -- Executing [123456@incoming:2] Playback("999@2002-0", "beep") in new stack
   -- <999@2002-0> Playing 'beep.gsm' (language 'en')
   -- Executing [123456@incoming:3] Wait("999@2002-0", "4") in new stack
   -- Executing [123456@incoming:4] Hangup("999@2002-0", "") in new stack
 == Spawn extension (incoming, 123456, 4) exited non-zero on '999@2002-0'
USTM(999@2002-0) channel already destroyed

# unistim.conf
[general]
port=4100
bindaddr=0.0.0.0

[2002]
device=000AE475AD4B
rtp_port=10000
rtp_method=3
status_method=0
titledefault=TEST
height=1
country=us
ringvolume=2
ringstyle=3
callhistory=1
callerid="Customer Support" <555-234-5678>
context=incoming
linelabel="Support"
extension=line
line => 999
Comments:By: Igor Goncharovsky (igorg) 2010-12-28 23:23:46.000-0600

There is problem in 1.8, where sin_family is not set properly. You can look into path in issue 0018229 and found where sin_family set to AF_INET (there is approximately 3 places in handleCallOutgoins and start_rtp functions).
By: Leif Madsen (lmadsen) 2011-01-04 15:24:44.000-0600

For the crashes you'll need to provide backtraces.
By: Teq (tequ) 2011-01-07 09:47:27.000-0600

Patch chan_unistim.c.r299906-6.diff solved the problem. GJ.