Quantcast
Channel: Asterisk Forums
Viewing all 7460 articles
Browse latest View live

Asterisk Consol stops working at 140+ calls

$
0
0
If you are leaking file descriptors, doing do a bash ls on /proc/nnn/fd, where nnn is the PID of Asterisk, should not result in a continual increase in the number of pseudo files listed. If you are leaking some other resource, you will have to do an appropriate measurement (ps -l will tell you if you are leaking memory).

A resource leak would indicate a bug, in which case you may have to upgrade Asterisk or submit a but report and wait for it to be fixed, depending on whether it is a known or unknown bug.

Statistics : Posted by kamrul.khan • on Fri Jan 03, 2014 1:08 am • Replies 5 • Views 183

Asterisk Consol stops working at 140+ calls

$
0
0
david55 wrote:Do you have a resource leak?


How do I check ?

Statistics : Posted by kamrul.khan • on Fri Jan 03, 2014 1:08 am • Replies 5 • Views 183

Asterisk Consol stops working at 140+ calls

$
0
0
Hi,

Thanks for your reply. We have updated the ulimit. Initially it was set to 1024. We updated it to 65536. But still we are facing the same issue. We got the below error from the log during the time of occurrence.

Code: [Jan 10 18:59:59] ERROR[6394] acl.c: Cannot create socket
[Jan 10 18:59:59] WARNING[6394] res_rtp_asterisk.c: Unable to allocate RTP socket: Too many open files



ulimit -a gives

Code: # ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 256523
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 65536
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 256523
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited



We are really in trouble with this issue. Please help us. Thanks in advance.

Statistics : Posted by kamrul.khan • on Fri Jan 03, 2014 1:08 am • Replies 5 • Views 183

Asterisk Consol stops working at 140+ calls

$
0
0
Do you have a resource leak?

Statistics : Posted by kamrul.khan • on Fri Jan 03, 2014 1:08 am • Replies 5 • Views 183

Asterisk Consol stops working at 140+ calls

$
0
0
I assume you have run out of some system resource. I'd check you don't have any effective limit on open file descriptors, but otherwise you will need to determine if asterisk -r is crashing, in which case you will need a backtrace, or you will need to do a system call trace to get an idea of where it is failing.

Statistics : Posted by kamrul.khan • on Fri Jan 03, 2014 1:08 am • Replies 5 • Views 183

Asterisk Consol stops working at 140+ calls

$
0
0
Hi,

We have this problem in our Asterisk server. When number of active calls reaches around 140 we can no more connect to asterisk console. asterisk -r only shows the welcome message and then exits to shell automatically.

We have Intel E3-1245 4 core processor with 32 GB RAM. CPU usages goes around 40-42% when this kind of situation arises. We also found that the server doesnt actually drop any calls but we simply cant monitor our server when this kind of situation arises.

Please give us some clue like what can be the cause of this problem and how can we fix it. Let us know if you need any further details.

Thanks in advanced!

Statistics : Posted by kamrul.khan • on Fri Jan 03, 2014 1:08 am • Replies 5 • Views 183

Asterisk Manager Interface (AMI) With DAHDI system.conf

$
0
0
Yeah, not supported. Asterisk never reads or processes the files in /etc/dahdi itself, so shouldn't need to have any knowledge of those files.

Statistics : Posted by kartus517 • on Fri Jan 10, 2014 2:25 pm • Replies 1 • Views 33

Asterisk Manager Interface (AMI) With DAHDI system.conf

$
0
0
I am trying to edit system.conf via AMI UpdateConfig command. But since /etc/dahdi/system.conf does not have standard configuration file format as others (eg. extens.conf, chan_dahdi.conf), AMI always throws back this error to me. Any idea how it can be resolved, or am I trying something which is not supported.

Statistics : Posted by kartus517 • on Fri Jan 10, 2014 2:25 pm • Replies 1 • Views 33

External calls can't be answered or declined

$
0
0
Hi all,

Setup: Asterisk 11 server on Centos 6.4 64bit, and it runs fine. And I'm new to Asterisk.

Calling between internal extensions works fine and presents no issues. But there is an issue with calls to/from the outside world, in that the status of the call (answered, declined) doesn't seem to be passed along. For example, if I call from x1001 to 555-555-5555, the call can be answered with working audio and speech but it dies after 30 seconds. And if the call is declined, the server still attempts to connect the call until the 30-second mark is reached (ie - even if declined, the server will continue to ring the line).

I understand that the 30 seconds mark is from a default that is setting the amount of time to attempt a call. The real issue I am trying to determine is why the status of the call (answered, declined) isn't being transmitted to/from the outside world. I am 99.99% sure it is a simple server configuration issue that I have overlooked, but I don't know exactly what needs changed. Obviously a critical response of some sort is not being passed along.

To bridge from the Asterisk server to the outside world, I am using Twilio.

Sip.conf:

Code: [xlite1]
; This is extension 1001
type=friend
host=dynamic
username=xlite1
remotesecret=<a_password_here>
transport=udp,tcp
context=dialphones

[xlite2]
; This is extension 1002
type=friend
host=dynamic
username=xlite2
remotesecret=<a_password_here>
tranport=udp,tcp
context=dialphones

[twilio]
type=friend
username=twilio
password=<a_password_here>
host=<my_twilio_sip_domain>
qualify=no

[twiliocaller](!)
type=peer
qualify=no
allowguest=yes
context=dialphones

; And I have an entry like this for each Twilio IP that should be allowed access.
; eg: [twilioip-1], [twilioip-2] .... [twilioip-23]
[twilioip-1](twiliocaller)
host=107.21.222.153


Extensions.conf:
Code: [dialphones]
; If starting with a 9, dial the outside world
exten => _9.,1,Dial(SIP/{$EXTEN:1}@twilio)

[public]
include => demo

exten => 1001,1,Dial(SIP/xlite1)
exten => 1002,1,Dial(SIP/xlite2)


Here is the CLI output during a call, that is answered, from x1001 to 555-555-5555. (Yes, I am using a real phone number when testing this, but I'm not posting it here, of course.). The output is the same whether the call is answered or declined.

Code: testserver*CLI>
== Using SIP RTP CoS mark 5
-- Executing [915555555555@dialphones:1] Dial("SIP/xlite1-0000000d", "SIP/{$EXTEN:1}@twilio") in new stack
== Using SIP RTP CoS mark 5
-- Called SIP/{$EXTEN:1}@twilio
-- SIP/twilio-0000000e is ringing
-- SIP/twilio-0000000e answered SIP/xlite1-0000000d
-- Remotely bridging SIP/xlite1-0000000d and SIP/twilio-0000000e
testserver*CLI>


Traffic captures of a call from x1001 to 555-555-5555 that is answered or declined looks identical. In the following I've made the data anonymous, so here is the legend:
    1.) 111.111.111.111 is the IP address of my Asterisk server, which is my.asterisk.server.com
    2.) 222.222.222.222 is the IP address of the xlite1 client
    3.) 107.21.222.153 is the IP address of the Twilio SIP server passing the information

Code: 49.467973 222.222.222.222 -> 111.111.111.111 SIP/SDP 937 Request: INVITE sip:915555555555@my.asterisk.server.com | , with session description
49.469001 111.111.111.111 -> 222.222.222.222 SIP 574 Status: 100 Trying |
49.470174 111.111.111.111 -> 107.21.222.153 SIP/SDP 918 Request: INVITE sip:%7B$EXTEN@my_twilio_sip_domain.sip.twilio.com | , with session description
49.547463 107.21.222.153 -> 111.111.111.111 SIP 355 Status: 100 Giving a try |
50.565114 107.21.222.153 -> 111.111.111.111 SIP 533 Status: 180 Ringing |
50.565767 111.111.111.111 -> 222.222.222.222 SIP 590 Status: 180 Ringing |
51.102807 107.21.222.153 -> 111.111.111.111 SIP/SDP 812 Status: 200 OK | , with session description
51.103428 111.111.111.111 -> 107.21.222.153 SIP 542 Request: ACK sip:10.70.227.82:5060 |
51.103741 111.111.111.111 -> 222.222.222.222 SIP/SDP 881 Status: 200 OK | , with session description
51.104083 111.111.111.111 -> 107.21.222.153 SIP/SDP 929 Request: INVITE sip:10.70.227.82:5060 | , with session description
51.181029 107.21.222.153 -> 111.111.111.111 SIP 414 Status: 100 Giving a try |
51.265552 107.21.222.153 -> 111.111.111.111 SIP/SDP 735 Status: 200 OK | , with session description
51.266103 111.111.111.111 -> 107.21.222.153 SIP 542 Request: ACK sip:10.70.227.82:5060 |
51.298501 222.222.222.222 -> 111.111.111.111 SIP 503 Request: ACK sip:915555555555@111.111.111.111:5060 |
51.298812 111.111.111.111 -> 222.222.222.222 SIP/SDP 852 Request: INVITE sip:xlite1@222.222.222.222:23924 | , with session description
51.310028 222.222.222.222 -> 111.111.111.111 UDP 46 Source port: 23924Destination port: sip
51.318159 222.222.222.222 -> 111.111.111.111 SIP/SDP 792 Status: 200 OK | , with session description
51.318646 111.111.111.111 -> 222.222.222.222 SIP 465 Request: ACK sip:xlite1@222.222.222.222:23924 |
51.318877 111.111.111.111 -> 107.21.222.153 SIP/SDP 929 Request: INVITE sip:10.70.227.82:5060 | , with session description
51.395861 107.21.222.153 -> 111.111.111.111 SIP 414 Status: 100 Giving a try |
51.477794 107.21.222.153 -> 111.111.111.111 SIP/SDP 737 Status: 200 OK | , with session description
51.478255 111.111.111.111 -> 107.21.222.153 SIP 542 Request: ACK sip:10.70.227.82:5060 |


And here is a traffic capture of a call between xlite1 (x1001) and xlite2 (x1002). As I said before, these give me no issues. But I'm providing them for trouble shooting purposes in case it helps any of you answer my question.

Code: 36.489786 111.111.111.111 -> 222.222.222.222 SIP/SDP 963 Request: INVITE sip:xlite1@222.222.222.222:23924;rinstance=21bd309ac44c2a5d | , with session description
36.631336 222.222.222.222 -> 111.111.111.111 SIP 348 Status: 100 Trying |
36.663837 222.222.222.222 -> 111.111.111.111 SIP 473 Status: 180 Ringing |
36.664360 111.111.111.111 -> 222.222.222.222 SIP 576 Status: 180 Ringing |
41.150921 222.222.222.222 -> 111.111.111.111 SIP/SDP 804 Status: 200 OK | , with session description
41.151619 111.111.111.111 -> 222.222.222.222 SIP 474 Request: ACK sip:xlite1@222.222.222.222:23924 |
41.151966 111.111.111.111 -> 222.222.222.222 SIP/SDP 869 Status: 200 OK | , with session description
41.152278 111.111.111.111 -> 222.222.222.222 SIP/SDP 885 Request: INVITE sip:xlite1@222.222.222.222:23924 | , with session description
41.208076 222.222.222.222 -> 111.111.111.111 SIP 491 Request: ACK sip:1001@111.111.111.111:5060 |
41.209060 111.111.111.111 -> 222.222.222.222 SIP/SDP 863 Request: INVITE sip:xlite@222.222.222.222:30148 | , with session description
41.245060 222.222.222.222 -> 111.111.111.111 SIP/SDP 792 Status: 200 OK | , with session description
41.245601 111.111.111.111 -> 222.222.222.222 SIP 452 Request: ACK sip:xlite@222.222.222.222:30148 |
41.277649 222.222.222.222 -> 111.111.111.111 SIP/SDP 804 Status: 200 OK | , with session description
41.278246 111.111.111.111 -> 222.222.222.222 SIP 474 Request: ACK sip:xlite1@222.222.222.222:23924 |
41.278455 111.111.111.111 -> 222.222.222.222 SIP/SDP 885 Request: INVITE sip:xlite1@222.222.222.222:23924 | , with session description
41.297150 222.222.222.222 -> 111.111.111.111 SIP/SDP 804 Status: 200 OK | , with session description
41.297548 111.111.111.111 -> 222.222.222.222 SIP 474 Request: ACK sip:xlite1@222.222.222.222:23924 |


Statistics : Posted by pk71p • on Sat Jan 11, 2014 9:02 pm • Replies 1 • Views 58

WebRTC & Asterisk 11.7.0 - not hear audio

$
0
0
wacky wrote:@navaismo, thanks for reply

My laptop (client) with Google Chrome - 192.168.51.3
My Asterisk - 192.168.51.9

So this is LAN to LAN, your first RTP debug show a Public IP, you need to fix that. Check your Asterisk peer's settings about NAT and in the JsSIP API check the ICE or use the workaorund, setting ICE server to null.

Quote:How check it is?

Install the libraries, re run the configure script and recompile asterisk.

Quote:Its my debug:

Code: JsSIP | UA | configuration parameters after validation: jssip-devel.js:5783
· via_host: "peiululf5p51.invalid" jssip-devel.js:5794
· password: NOT SHOWN jssip-devel.js:5791
· register_expires: 600 jssip-devel.js:5794
· register_min_expires: 120 jssip-devel.js:5794
· register: true jssip-devel.js:5794
· registrar_server: sip:192.168.51.9 jssip-devel.js:5788
· ws_server_max_reconnection: 3 jssip-devel.js:5794
· ws_server_reconnection_timeout: 4 jssip-devel.js:5794
· connection_recovery_min_interval: 2 jssip-devel.js:5794
· connection_recovery_max_interval: 30 jssip-devel.js:5794
· use_preloaded_route: false jssip-devel.js:5794
· no_answer_timeout: 60000 jssip-devel.js:5794
· stun_servers: ["stun:stun.l.google.com:19302"] jssip-devel.js:5794
· turn_servers: [] jssip-devel.js:5794
· trace_sip: true jssip-devel.js:5794
· hack_via_tcp: false jssip-devel.js:5794
· hack_ip_in_contact: false jssip-devel.js:5794
· uri: sip:100@192.168.51.9 jssip-devel.js:5788
· ws_servers: [{"ws_uri":"ws://192.168.51.9:8088/ws","sip_uri":"<sip:192.168.51.9:8088;transport=ws;lr>","weight":0,"status":0,"scheme":"WS"}] jssip-devel.js:5794
· display_name: "100" jssip-devel.js:5794
· instance_id: "7caae24a-d71b-468f-a7c5-0d09c41667db" jssip-devel.js:5794
· jssip_id: "c4j7i" jssip-devel.js:5794
· hostport_params: "192.168.51.9" jssip-devel.js:5794
· authorization_user: "100" jssip-devel.js:5794
JsSIP | EVENT EMITTER | adding event newMessage jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event newRTCSession jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event registrationFailed jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event unregistered jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event registered jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event disconnected jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event connected jssip-devel.js:67
JsSIP | EVENT EMITTER | new listener added to event connected jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event disconnected jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event newRTCSession jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event newMessage jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event registered jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event unregistered jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event registrationFailed jssip-devel.js:63
JsSIP | UA | user requested startup... jssip-devel.js:5238
JsSIP | TRANSPORT | connecting to WebSocket ws://192.168.51.9:8088/ws jssip-devel.js:568
JsSIP | TRANSPORT | WebSocket ws://192.168.51.9:8088/ws connected jssip-devel.js:604
JsSIP | UA | connection state set to 0 jssip-devel.js:5360
JsSIP | EVENT EMITTER | emitting event connected jssip-devel.js:187
JsSIP | TRANSPORT | sending WebSocket message:

REGISTER sip:192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK7503800
Max-Forwards: 69
To: <sip:100@192.168.51.9>
From: "100" <sip:100@192.168.51.9>;tag=95kc5hfjkn
Call-ID: ushk79hn4ettqgpopuuj2q
CSeq: 81 REGISTER
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:7caae24a-d71b-468f-a7c5-0d09c41667db>";expires=600
Allow: ACK,CANCEL,BYE,OPTIONS,INVITE,MESSAGE
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 0


jssip-devel.js:519
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 401 Unauthorized
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK7503800;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=95kc5hfjkn
To: <sip:100@192.168.51.9>;tag=as51e206b9
Call-ID: ushk79hn4ettqgpopuuj2q
CSeq: 81 REGISTER
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="3d66d490"
Content-Length: 0


jssip-devel.js:686
JsSIP | TRANSPORT | sending WebSocket message:

REGISTER sip:192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6637211
Max-Forwards: 69
To: <sip:100@192.168.51.9>
From: "100" <sip:100@192.168.51.9>;tag=95kc5hfjkn
Call-ID: ushk79hn4ettqgpopuuj2q
CSeq: 82 REGISTER
Authorization: Digest algorithm=MD5, username="100", realm="asterisk", nonce="3d66d490", uri="sip:192.168.51.9", response="2930f180b852ac955bf64740125db4bb"
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:7caae24a-d71b-468f-a7c5-0d09c41667db>";expires=600
Allow: ACK,CANCEL,BYE,OPTIONS,INVITE,MESSAGE
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 0


jssip-devel.js:519
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 200 OK
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6637211;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=95kc5hfjkn
To: <sip:100@192.168.51.9>;tag=as51e206b9
Call-ID: ushk79hn4ettqgpopuuj2q
CSeq: 82 REGISTER
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 600
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws>;expires=600
Date: Sun, 12 Jan 2014 20:28:19 GMT
Content-Length: 0


jssip-devel.js:686
JsSIP | EVENT EMITTER | emitting event registered jssip-devel.js:187
Registered init.js:425
JsSIP | EVENT EMITTER | adding event newDTMF jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event ended jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event started jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event failed jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event progress jssip-devel.js:67
JsSIP | EVENT EMITTER | emitting event newRTCSession jssip-devel.js:187
JsSIP | RTC SESSION | requesting access to local media jssip-devel.js:3442
JsSIP | EVENT EMITTER | new listener added to event progress jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event started jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event failed jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event newDTMF jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event ended jssip-devel.js:63
JsSIP | RTC SESSION | got local media stream jssip-devel.js:3446
JsSIP | RTC SESSION | ICE candidate received: a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
jssip-devel.js:3401
JsSIP | TRANSPORT | sending WebSocket message:

INVITE sip:100@192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6014657
Max-Forwards: 69
To: <sip:100@192.168.51.9>
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2142 INVITE
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INVITE,MESSAGE
Content-Type: application/sdp
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 3276

v=0
o=- 6843435261791628335 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio video
a=msid-semantic: WMS KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
m=audio 50270 RTP/SAVPF 111 103 104 0 8 106 105 13 126
c=IN IP4 95.160.158.151
a=rtcp:50270 IN IP4 95.160.158.151
a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=ice-ufrag:1YUrMq93Rc3A1O1d
a=ice-pwd:3IKU0LhB6+rJfnVtys+cpfCp
a=ice-options:google-ice
a=fingerprint:sha-256 AA:AB:A9:E2:B9:20:71:19:8B:12:67:18:11:30:B8:CD:3E:EE:80:80:99:0C:54:FC:7B:61:4D:75:66:CE:9A:AA
a=setup:actpass
a=mid:audio
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=sendrecv
a=rtcp-mux
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:AQieWl3A0ztd+fcOU2egvVmvtL8vemnFnzSQ82fD
a=rtpmap:111 opus/48000/2
a=fmtp:111 minptime=10
a=rtpmap:103 ISAC/16000
a=rtpmap:104 ISAC/32000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:106 CN/32000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:126 telephone-event/8000
a=maxptime:60
a=ssrc:2465071814 cname:WDkgccFsgfpOoGcI
a=ssrc:2465071814 msid:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHa0
a=ssrc:2465071814 mslabel:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
a=ssrc:2465071814 label:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHa0
m=video 50270 RTP/SAVPF 100 116 117
c=IN IP4 95.160.158.151
a=rtcp:50270 IN IP4 95.160.158.151
a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=ice-ufrag:1YUrMq93Rc3A1O1d
a=ice-pwd:3IKU0LhB6+rJfnVtys+cpfCp
a=ice-options:google-ice
a=fingerprint:sha-256 AA:AB:A9:E2:B9:20:71:19:8B:12:67:18:11:30:B8:CD:3E:EE:80:80:99:0C:54:FC:7B:61:4D:75:66:CE:9A:AA
a=setup:actpass
a=mid:video
a=extmap:2 urn:ietf:params:rtp-hdrext:toffset
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=sendrecv
a=rtcp-mux
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:AQieWl3A0ztd+fcOU2egvVmvtL8vemnFnzSQ82fD
a=rtpmap:100 VP8/90000
a=rtcp-fb:100 ccm fir
a=rtcp-fb:100 nack
a=rtcp-fb:100 goog-remb
a=rtpmap:116 red/90000
a=rtpmap:117 ulpfec/90000
a=ssrc:1336778605 cname:WDkgccFsgfpOoGcI
a=ssrc:1336778605 msid:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHv0
a=ssrc:1336778605 mslabel:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
a=ssrc:1336778605 label:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHv0

jssip-devel.js:519
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 401 Unauthorized
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6014657;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
To: <sip:100@192.168.51.9>;tag=as06fb6d4e
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2142 INVITE
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="5fbb46dd"
Content-Length: 0


jssip-devel.js:686
JsSIP | TRANSPORT | sending WebSocket message:

ACK sip:100@192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6014657
To: <sip:100@192.168.51.9>;tag=as06fb6d4e
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2142 ACK


jssip-devel.js:519
JsSIP | TRANSPORT | sending WebSocket message:

INVITE sip:100@192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK5050190
Max-Forwards: 69
To: <sip:100@192.168.51.9>
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2143 INVITE
Authorization: Digest algorithm=MD5, username="100", realm="asterisk", nonce="5fbb46dd", uri="sip:100@192.168.51.9", response="044d12332d9e0c16f44e6aa9999d651f"
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INVITE,MESSAGE
Content-Type: application/sdp
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 3276

v=0
o=- 6843435261791628335 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio video
a=msid-semantic: WMS KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
m=audio 50270 RTP/SAVPF 111 103 104 0 8 106 105 13 126
c=IN IP4 95.160.158.151
a=rtcp:50270 IN IP4 95.160.158.151
a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=ice-ufrag:1YUrMq93Rc3A1O1d
a=ice-pwd:3IKU0LhB6+rJfnVtys+cpfCp
a=ice-options:google-ice
a=fingerprint:sha-256 AA:AB:A9:E2:B9:20:71:19:8B:12:67:18:11:30:B8:CD:3E:EE:80:80:99:0C:54:FC:7B:61:4D:75:66:CE:9A:AA
a=setup:actpass
a=mid:audio
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=sendrecv
a=rtcp-mux
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:AQieWl3A0ztd+fcOU2egvVmvtL8vemnFnzSQ82fD
a=rtpmap:111 opus/48000/2
a=fmtp:111 minptime=10
a=rtpmap:103 ISAC/16000
a=rtpmap:104 ISAC/32000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:106 CN/32000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:126 telephone-event/8000
a=maxptime:60
a=ssrc:2465071814 cname:WDkgccFsgfpOoGcI
a=ssrc:2465071814 msid:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHa0
a=ssrc:2465071814 mslabel:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
a=ssrc:2465071814 label:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHa0
m=video 50270 RTP/SAVPF 100 116 117
c=IN IP4 95.160.158.151
a=rtcp:50270 IN IP4 95.160.158.151
a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=ice-ufrag:1YUrMq93Rc3A1O1d
a=ice-pwd:3IKU0LhB6+rJfnVtys+cpfCp
a=ice-options:google-ice
a=fingerprint:sha-256 AA:AB:A9:E2:B9:20:71:19:8B:12:67:18:11:30:B8:CD:3E:EE:80:80:99:0C:54:FC:7B:61:4D:75:66:CE:9A:AA
a=setup:actpass
a=mid:video
a=extmap:2 urn:ietf:params:rtp-hdrext:toffset
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=sendrecv
a=rtcp-mux
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:AQieWl3A0ztd+fcOU2egvVmvtL8vemnFnzSQ82fD
a=rtpmap:100 VP8/90000
a=rtcp-fb:100 ccm fir
a=rtcp-fb:100 nack
a=rtcp-fb:100 goog-remb
a=rtpmap:116 red/90000
a=rtpmap:117 ulpfec/90000
a=ssrc:1336778605 cname:WDkgccFsgfpOoGcI
a=ssrc:1336778605 msid:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHv0
a=ssrc:1336778605 mslabel:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
a=ssrc:1336778605 label:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHv0

jssip-devel.js:519
JsSIP | TRANSACTION | Timer D expired for INVITE client transaction z9hG4bK6014657 jssip-devel.js:1969
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 100 Trying
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK5050190;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
To: <sip:100@192.168.51.9>
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2143 INVITE
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:100@192.168.51.9:5060;transport=WS>
Content-Length: 0


jssip-devel.js:686
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 200 OK
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK5050190;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
To: <sip:100@192.168.51.9>;tag=as77392278
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2143 INVITE
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:100@192.168.51.9:5060;transport=WS>
Content-Type: application/sdp
Content-Length: 403

v=0
o=root 703073431 703073431 IN IP4 192.168.51.9
s=Asterisk PBX 11.7.0
c=IN IP4 192.168.51.9
t=0 0
m=audio 11092 RTP/SAVPF 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:6m4OuyQDFTxime0a9uRrpL8kSskPEyyzZZJ9v/fJ
m=video 0 RTP/SAVPF 100 116 117

jssip-devel.js:686
JsSIP | DIALOG | new UAC dialog created with status CONFIRMED jssip-devel.js:2546
JsSIP | RTC SESSION | stream added: default jssip-devel.js:3392
JsSIP | TRANSPORT | sending WebSocket message:

ACK sip:100@192.168.51.9:5060;transport=ws SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK3482275
Max-Forwards: 69
To: <sip:100@192.168.51.9>;tag=as77392278
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2143 ACK
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 0


jssip-devel.js:519
JsSIP | EVENT EMITTER | emitting event started jssip-devel.js:187
JsSIP | TRANSPORT | received WebSocket text message:

BYE sip:duu35udr@peiululf5p51.invalid;transport=ws;ob SIP/2.0
Via: SIP/2.0/WS 192.168.51.9:5060;branch=z9hG4bK3df6ce15
Max-Forwards: 70
From: <sip:100@192.168.51.9>;tag=as77392278
To: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 102 BYE
User-Agent: Asterisk PBX 11.7.0
Proxy-Authorization: Digest username="r8oumeb5", realm="asterisk", algorithm=MD5, uri="sip:192.168.51.9", nonce="5fbb46dd", response="f746171f1fe50942d851a894252db743"
X-Asterisk-HangupCause: Unknown
X-Asterisk-HangupCauseCode: 0
Content-Length: 0


jssip-devel.js:686
JsSIP | TRANSPORT | sending WebSocket message:

SIP/2.0 200 OK
Via: SIP/2.0/WS 192.168.51.9:5060;branch=z9hG4bK3df6ce15
To: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
From: <sip:100@192.168.51.9>;tag=as77392278
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 102 BYE
Content-Length: 0


jssip-devel.js:519
JsSIP | RTC SESSION | closing INVITE session c4j7imnqn2u69938mpb66d4c8jqn3k jssip-devel.js:4248
JsSIP | RTC SESSION | closing PeerConnection jssip-devel.js:3424
JsSIP | DIALOG | dialog c4j7imnqn2u69938mpb66d4c8jqn3kas77392278 deleted jssip-devel.js:2566
JsSIP | EVENT EMITTER | emitting event ended jssip-devel.js:187
JsSIP | TRANSACTION | Timer J expired for non-INVITE server transaction z9hG4bK3df6ce15 jssip-devel.js:2094
JsSIP | TRANSACTION | Timer B expired for INVITE client transaction z9hG4bK5050190 jssip-devel.js:1960
JsSIP | TRANSACTION | Timer M expired for INVITE client transaction z9hG4bK5050190 jssip-devel.js:1949


You debug show a Public IP and you need to provide both logs, so try first fixing the NAT/ICE stuff.

Statistics : Posted by wacky • on Sun Jan 12, 2014 11:59 am • Replies 3 • Views 74

WebRTC & Asterisk 11.7.0 - not hear audio

$
0
0
@navaismo, thanks for reply

My laptop (client) with Google Chrome - 192.168.51.3
My Asterisk - 192.168.51.9

Quote:2) Validate that your Asterisk is compiled with the uuid-devel/libuuid-devel libraries in order to enable ICE(your rtp doesnt show the label "via ICE")


How check it is?


Its my debug:

Code: JsSIP | UA | configuration parameters after validation: jssip-devel.js:5783
· via_host: "peiululf5p51.invalid" jssip-devel.js:5794
· password: NOT SHOWN jssip-devel.js:5791
· register_expires: 600 jssip-devel.js:5794
· register_min_expires: 120 jssip-devel.js:5794
· register: true jssip-devel.js:5794
· registrar_server: sip:192.168.51.9 jssip-devel.js:5788
· ws_server_max_reconnection: 3 jssip-devel.js:5794
· ws_server_reconnection_timeout: 4 jssip-devel.js:5794
· connection_recovery_min_interval: 2 jssip-devel.js:5794
· connection_recovery_max_interval: 30 jssip-devel.js:5794
· use_preloaded_route: false jssip-devel.js:5794
· no_answer_timeout: 60000 jssip-devel.js:5794
· stun_servers: ["stun:stun.l.google.com:19302"] jssip-devel.js:5794
· turn_servers: [] jssip-devel.js:5794
· trace_sip: true jssip-devel.js:5794
· hack_via_tcp: false jssip-devel.js:5794
· hack_ip_in_contact: false jssip-devel.js:5794
· uri: sip:100@192.168.51.9 jssip-devel.js:5788
· ws_servers: [{"ws_uri":"ws://192.168.51.9:8088/ws","sip_uri":"<sip:192.168.51.9:8088;transport=ws;lr>","weight":0,"status":0,"scheme":"WS"}] jssip-devel.js:5794
· display_name: "100" jssip-devel.js:5794
· instance_id: "7caae24a-d71b-468f-a7c5-0d09c41667db" jssip-devel.js:5794
· jssip_id: "c4j7i" jssip-devel.js:5794
· hostport_params: "192.168.51.9" jssip-devel.js:5794
· authorization_user: "100" jssip-devel.js:5794
JsSIP | EVENT EMITTER | adding event newMessage jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event newRTCSession jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event registrationFailed jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event unregistered jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event registered jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event disconnected jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event connected jssip-devel.js:67
JsSIP | EVENT EMITTER | new listener added to event connected jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event disconnected jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event newRTCSession jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event newMessage jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event registered jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event unregistered jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event registrationFailed jssip-devel.js:63
JsSIP | UA | user requested startup... jssip-devel.js:5238
JsSIP | TRANSPORT | connecting to WebSocket ws://192.168.51.9:8088/ws jssip-devel.js:568
JsSIP | TRANSPORT | WebSocket ws://192.168.51.9:8088/ws connected jssip-devel.js:604
JsSIP | UA | connection state set to 0 jssip-devel.js:5360
JsSIP | EVENT EMITTER | emitting event connected jssip-devel.js:187
JsSIP | TRANSPORT | sending WebSocket message:

REGISTER sip:192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK7503800
Max-Forwards: 69
To: <sip:100@192.168.51.9>
From: "100" <sip:100@192.168.51.9>;tag=95kc5hfjkn
Call-ID: ushk79hn4ettqgpopuuj2q
CSeq: 81 REGISTER
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:7caae24a-d71b-468f-a7c5-0d09c41667db>";expires=600
Allow: ACK,CANCEL,BYE,OPTIONS,INVITE,MESSAGE
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 0


jssip-devel.js:519
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 401 Unauthorized
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK7503800;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=95kc5hfjkn
To: <sip:100@192.168.51.9>;tag=as51e206b9
Call-ID: ushk79hn4ettqgpopuuj2q
CSeq: 81 REGISTER
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="3d66d490"
Content-Length: 0


jssip-devel.js:686
JsSIP | TRANSPORT | sending WebSocket message:

REGISTER sip:192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6637211
Max-Forwards: 69
To: <sip:100@192.168.51.9>
From: "100" <sip:100@192.168.51.9>;tag=95kc5hfjkn
Call-ID: ushk79hn4ettqgpopuuj2q
CSeq: 82 REGISTER
Authorization: Digest algorithm=MD5, username="100", realm="asterisk", nonce="3d66d490", uri="sip:192.168.51.9", response="2930f180b852ac955bf64740125db4bb"
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws>;reg-id=1;+sip.instance="<urn:uuid:7caae24a-d71b-468f-a7c5-0d09c41667db>";expires=600
Allow: ACK,CANCEL,BYE,OPTIONS,INVITE,MESSAGE
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 0


jssip-devel.js:519
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 200 OK
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6637211;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=95kc5hfjkn
To: <sip:100@192.168.51.9>;tag=as51e206b9
Call-ID: ushk79hn4ettqgpopuuj2q
CSeq: 82 REGISTER
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Expires: 600
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws>;expires=600
Date: Sun, 12 Jan 2014 20:28:19 GMT
Content-Length: 0


jssip-devel.js:686
JsSIP | EVENT EMITTER | emitting event registered jssip-devel.js:187
Registered init.js:425
JsSIP | EVENT EMITTER | adding event newDTMF jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event ended jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event started jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event failed jssip-devel.js:67
JsSIP | EVENT EMITTER | adding event progress jssip-devel.js:67
JsSIP | EVENT EMITTER | emitting event newRTCSession jssip-devel.js:187
JsSIP | RTC SESSION | requesting access to local media jssip-devel.js:3442
JsSIP | EVENT EMITTER | new listener added to event progress jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event started jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event failed jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event newDTMF jssip-devel.js:63
JsSIP | EVENT EMITTER | new listener added to event ended jssip-devel.js:63
JsSIP | RTC SESSION | got local media stream jssip-devel.js:3446
JsSIP | RTC SESSION | ICE candidate received: a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
jssip-devel.js:3401
JsSIP | RTC SESSION | ICE candidate received: a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
jssip-devel.js:3401
JsSIP | TRANSPORT | sending WebSocket message:

INVITE sip:100@192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6014657
Max-Forwards: 69
To: <sip:100@192.168.51.9>
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2142 INVITE
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INVITE,MESSAGE
Content-Type: application/sdp
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 3276

v=0
o=- 6843435261791628335 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio video
a=msid-semantic: WMS KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
m=audio 50270 RTP/SAVPF 111 103 104 0 8 106 105 13 126
c=IN IP4 95.160.158.151
a=rtcp:50270 IN IP4 95.160.158.151
a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=ice-ufrag:1YUrMq93Rc3A1O1d
a=ice-pwd:3IKU0LhB6+rJfnVtys+cpfCp
a=ice-options:google-ice
a=fingerprint:sha-256 AA:AB:A9:E2:B9:20:71:19:8B:12:67:18:11:30:B8:CD:3E:EE:80:80:99:0C:54:FC:7B:61:4D:75:66:CE:9A:AA
a=setup:actpass
a=mid:audio
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=sendrecv
a=rtcp-mux
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:AQieWl3A0ztd+fcOU2egvVmvtL8vemnFnzSQ82fD
a=rtpmap:111 opus/48000/2
a=fmtp:111 minptime=10
a=rtpmap:103 ISAC/16000
a=rtpmap:104 ISAC/32000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:106 CN/32000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:126 telephone-event/8000
a=maxptime:60
a=ssrc:2465071814 cname:WDkgccFsgfpOoGcI
a=ssrc:2465071814 msid:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHa0
a=ssrc:2465071814 mslabel:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
a=ssrc:2465071814 label:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHa0
m=video 50270 RTP/SAVPF 100 116 117
c=IN IP4 95.160.158.151
a=rtcp:50270 IN IP4 95.160.158.151
a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=ice-ufrag:1YUrMq93Rc3A1O1d
a=ice-pwd:3IKU0LhB6+rJfnVtys+cpfCp
a=ice-options:google-ice
a=fingerprint:sha-256 AA:AB:A9:E2:B9:20:71:19:8B:12:67:18:11:30:B8:CD:3E:EE:80:80:99:0C:54:FC:7B:61:4D:75:66:CE:9A:AA
a=setup:actpass
a=mid:video
a=extmap:2 urn:ietf:params:rtp-hdrext:toffset
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=sendrecv
a=rtcp-mux
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:AQieWl3A0ztd+fcOU2egvVmvtL8vemnFnzSQ82fD
a=rtpmap:100 VP8/90000
a=rtcp-fb:100 ccm fir
a=rtcp-fb:100 nack
a=rtcp-fb:100 goog-remb
a=rtpmap:116 red/90000
a=rtpmap:117 ulpfec/90000
a=ssrc:1336778605 cname:WDkgccFsgfpOoGcI
a=ssrc:1336778605 msid:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHv0
a=ssrc:1336778605 mslabel:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
a=ssrc:1336778605 label:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHv0

jssip-devel.js:519
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 401 Unauthorized
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6014657;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
To: <sip:100@192.168.51.9>;tag=as06fb6d4e
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2142 INVITE
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="5fbb46dd"
Content-Length: 0


jssip-devel.js:686
JsSIP | TRANSPORT | sending WebSocket message:

ACK sip:100@192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK6014657
To: <sip:100@192.168.51.9>;tag=as06fb6d4e
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2142 ACK


jssip-devel.js:519
JsSIP | TRANSPORT | sending WebSocket message:

INVITE sip:100@192.168.51.9 SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK5050190
Max-Forwards: 69
To: <sip:100@192.168.51.9>
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2143 INVITE
Authorization: Digest algorithm=MD5, username="100", realm="asterisk", nonce="5fbb46dd", uri="sip:100@192.168.51.9", response="044d12332d9e0c16f44e6aa9999d651f"
Contact: <sip:duu35udr@peiululf5p51.invalid;transport=ws;ob>
Allow: ACK,CANCEL,BYE,OPTIONS,INVITE,MESSAGE
Content-Type: application/sdp
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 3276

v=0
o=- 6843435261791628335 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio video
a=msid-semantic: WMS KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
m=audio 50270 RTP/SAVPF 111 103 104 0 8 106 105 13 126
c=IN IP4 95.160.158.151
a=rtcp:50270 IN IP4 95.160.158.151
a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=ice-ufrag:1YUrMq93Rc3A1O1d
a=ice-pwd:3IKU0LhB6+rJfnVtys+cpfCp
a=ice-options:google-ice
a=fingerprint:sha-256 AA:AB:A9:E2:B9:20:71:19:8B:12:67:18:11:30:B8:CD:3E:EE:80:80:99:0C:54:FC:7B:61:4D:75:66:CE:9A:AA
a=setup:actpass
a=mid:audio
a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
a=sendrecv
a=rtcp-mux
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:AQieWl3A0ztd+fcOU2egvVmvtL8vemnFnzSQ82fD
a=rtpmap:111 opus/48000/2
a=fmtp:111 minptime=10
a=rtpmap:103 ISAC/16000
a=rtpmap:104 ISAC/32000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:106 CN/32000
a=rtpmap:105 CN/16000
a=rtpmap:13 CN/8000
a=rtpmap:126 telephone-event/8000
a=maxptime:60
a=ssrc:2465071814 cname:WDkgccFsgfpOoGcI
a=ssrc:2465071814 msid:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHa0
a=ssrc:2465071814 mslabel:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
a=ssrc:2465071814 label:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHa0
m=video 50270 RTP/SAVPF 100 116 117
c=IN IP4 95.160.158.151
a=rtcp:50270 IN IP4 95.160.158.151
a=candidate:96503048 1 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:96503048 2 udp 2113937151 192.168.51.3 50270 typ host generation 0
a=candidate:1262713336 1 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:1262713336 2 tcp 1509957375 192.168.51.3 0 typ host generation 0
a=candidate:4090559708 1 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=candidate:4090559708 2 udp 1845501695 95.160.158.151 50270 typ srflx raddr 192.168.51.3 rport 50270 generation 0
a=ice-ufrag:1YUrMq93Rc3A1O1d
a=ice-pwd:3IKU0LhB6+rJfnVtys+cpfCp
a=ice-options:google-ice
a=fingerprint:sha-256 AA:AB:A9:E2:B9:20:71:19:8B:12:67:18:11:30:B8:CD:3E:EE:80:80:99:0C:54:FC:7B:61:4D:75:66:CE:9A:AA
a=setup:actpass
a=mid:video
a=extmap:2 urn:ietf:params:rtp-hdrext:toffset
a=extmap:3 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=sendrecv
a=rtcp-mux
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:AQieWl3A0ztd+fcOU2egvVmvtL8vemnFnzSQ82fD
a=rtpmap:100 VP8/90000
a=rtcp-fb:100 ccm fir
a=rtcp-fb:100 nack
a=rtcp-fb:100 goog-remb
a=rtpmap:116 red/90000
a=rtpmap:117 ulpfec/90000
a=ssrc:1336778605 cname:WDkgccFsgfpOoGcI
a=ssrc:1336778605 msid:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHv0
a=ssrc:1336778605 mslabel:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyH
a=ssrc:1336778605 label:KHzXoqxtMagGHpP2uvhv4mPqot1Fk9e4wgyHv0

jssip-devel.js:519
JsSIP | TRANSACTION | Timer D expired for INVITE client transaction z9hG4bK6014657 jssip-devel.js:1969
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 100 Trying
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK5050190;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
To: <sip:100@192.168.51.9>
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2143 INVITE
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:100@192.168.51.9:5060;transport=WS>
Content-Length: 0


jssip-devel.js:686
JsSIP | TRANSPORT | received WebSocket text message:

SIP/2.0 200 OK
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK5050190;received=192.168.51.3
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
To: <sip:100@192.168.51.9>;tag=as77392278
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2143 INVITE
Server: Asterisk PBX 11.7.0
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:100@192.168.51.9:5060;transport=WS>
Content-Type: application/sdp
Content-Length: 403

v=0
o=root 703073431 703073431 IN IP4 192.168.51.9
s=Asterisk PBX 11.7.0
c=IN IP4 192.168.51.9
t=0 0
m=audio 11092 RTP/SAVPF 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:6m4OuyQDFTxime0a9uRrpL8kSskPEyyzZZJ9v/fJ
m=video 0 RTP/SAVPF 100 116 117

jssip-devel.js:686
JsSIP | DIALOG | new UAC dialog created with status CONFIRMED jssip-devel.js:2546
JsSIP | RTC SESSION | stream added: default jssip-devel.js:3392
JsSIP | TRANSPORT | sending WebSocket message:

ACK sip:100@192.168.51.9:5060;transport=ws SIP/2.0
Via: SIP/2.0/WS peiululf5p51.invalid;branch=z9hG4bK3482275
Max-Forwards: 69
To: <sip:100@192.168.51.9>;tag=as77392278
From: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 2143 ACK
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.7
Content-Length: 0


jssip-devel.js:519
JsSIP | EVENT EMITTER | emitting event started jssip-devel.js:187
JsSIP | TRANSPORT | received WebSocket text message:

BYE sip:duu35udr@peiululf5p51.invalid;transport=ws;ob SIP/2.0
Via: SIP/2.0/WS 192.168.51.9:5060;branch=z9hG4bK3df6ce15
Max-Forwards: 70
From: <sip:100@192.168.51.9>;tag=as77392278
To: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 102 BYE
User-Agent: Asterisk PBX 11.7.0
Proxy-Authorization: Digest username="r8oumeb5", realm="asterisk", algorithm=MD5, uri="sip:192.168.51.9", nonce="5fbb46dd", response="f746171f1fe50942d851a894252db743"
X-Asterisk-HangupCause: Unknown
X-Asterisk-HangupCauseCode: 0
Content-Length: 0


jssip-devel.js:686
JsSIP | TRANSPORT | sending WebSocket message:

SIP/2.0 200 OK
Via: SIP/2.0/WS 192.168.51.9:5060;branch=z9hG4bK3df6ce15
To: "100" <sip:100@192.168.51.9>;tag=6d4c8jqn3k
From: <sip:100@192.168.51.9>;tag=as77392278
Call-ID: c4j7imnqn2u69938mpb6
CSeq: 102 BYE
Content-Length: 0


jssip-devel.js:519
JsSIP | RTC SESSION | closing INVITE session c4j7imnqn2u69938mpb66d4c8jqn3k jssip-devel.js:4248
JsSIP | RTC SESSION | closing PeerConnection jssip-devel.js:3424
JsSIP | DIALOG | dialog c4j7imnqn2u69938mpb66d4c8jqn3kas77392278 deleted jssip-devel.js:2566
JsSIP | EVENT EMITTER | emitting event ended jssip-devel.js:187
JsSIP | TRANSACTION | Timer J expired for non-INVITE server transaction z9hG4bK3df6ce15 jssip-devel.js:2094
JsSIP | TRANSACTION | Timer B expired for INVITE client transaction z9hG4bK5050190 jssip-devel.js:1960
JsSIP | TRANSACTION | Timer M expired for INVITE client transaction z9hG4bK5050190 jssip-devel.js:1949


Statistics : Posted by wacky • on Sun Jan 12, 2014 11:59 am • Replies 3 • Views 74

WebRTC & Asterisk 11.7.0 - not hear audio

$
0
0
Things to check:

1) The correct IP negotiation in the SDP of both Asterisk and JsSIP

2) Validate that your Asterisk is compiled with the uuid-devel/libuuid-devel libraries in order to enable ICE(your rtp doesnt show the label "via ICE").

3) If you are in the same LAN as the PBX check that the RTP audio goes to the LAN IP not to the Public IP, use the workaround in the JsSIP PI setting the STUN server to 'null'.

4) Provide both sip debug logs from JsSIP and Asterisk.

Statistics : Posted by wacky • on Sun Jan 12, 2014 11:59 am • Replies 3 • Views 74

WebRTC & Asterisk 11.7.0 - not hear audio

$
0
0
Hi, I have problem. I configure my asterisk with WebRPC. I use Asterisk 11.7.0 and tryit.jssip.net.

Connection is OK but I'am not hearing audio (playback and conversation)

please, help me Image

sip.conf
Code: ...
[100] ;webrpc
type=friend
secret=100
host=dynamic
context=michal
transport=udp,ws,wss
avpf=yes
encryption=yes
icesupport=yes
disallow=all
allow=alaw
allow=ulaw


extensions.conf:
Code: ...
[michal]
exten => _X.,1,Playback(tt-monkeys)
exten => _X.,1,Dial(SIP/${EXTEN})


http.conf:
Code: ...
bindaddr=0.0.0.0
enabled=yes
bindport=8088



CLI:
Quote:Connected to Asterisk 11.7.0 currently running on vbilling (pid = 3899)
vbilling*CLI> sip reload all
Reloading SIP
== Parsing '/etc/asterisk/sip.conf': Found
== Parsing '/etc/asterisk/users.conf': Found
== Using SIP CoS mark 4
== Parsing '/etc/asterisk/sip_notify.conf': Found
== Using SIP RTP CoS mark 5
-- Executing [111@michal:1] Playback("SIP/100-00000003", "tt-monkeys") in new stack
-- <SIP/100-00000003> Playing 'tt-monkeys.gsm' (language 'en')
vbilling*CLI>


it is playback but i not heard sound ;(

RTP debug:
Code: vbilling*CLI> rtp set debug on
RTP Debugging Enabled
  == Using SIP RTP CoS mark 5
    -- Executing [1111@michal:1] Playback("SIP/100-00000004", "tt-monkeys") in new stack
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031213, ts 000160, len 000164)
    -- <SIP/100-00000004> Playing 'tt-monkeys.gsm' (language 'en')
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031214, ts 000320, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031215, ts 000480, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031216, ts 000640, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031217, ts 000800, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031218, ts 000960, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031219, ts 001120, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031220, ts 001280, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031221, ts 001440, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031222, ts 001600, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031223, ts 001760, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031224, ts 001920, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031225, ts 002080, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031226, ts 002240, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031227, ts 002400, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031228, ts 002560, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031229, ts 002720, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031230, ts 002880, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031231, ts 003040, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031232, ts 003200, len 000164)
Sent RTP packet to      95.160.158.151:51326 (type 08, seq 031233, ts 003360, len 000164)
vbilling*CLI>


Statistics : Posted by wacky • on Sun Jan 12, 2014 11:59 am • Replies 3 • Views 74

Play sound file after each call

$
0
0
he h is the standard "hang-up" extension. The h extension, if it is configured, is called when a caller hangs up the phone. Note that as soon as this happens, the content of ${EXTEN} changes to h.

When the 'h' extension is running, the call legs have already been torn down. There is no way to delay this happening, and you can't do anything in the 'h' extension that needs to read audio from the channel (since no audio will appear, the first time it tries to read audio it will abort). Thus Playback() or Background(), for example, does not work. Essentially, the only things that make sense to use in the 'h' extension are those that don't have anything to do with the external channel that was involved before the hangup. No audio, no DTMF, etc.

Statistics : Posted by batteredveg • on Sun Jan 12, 2014 12:15 pm • Replies 1 • Views 32

Play sound file after each call

$
0
0
Hello folks

I've got what is (hopefully) a simple query; I know what code I need to use, but unsure of where I can put it to actually work.

At the end of every call (whether internal or external), I want a sound file to play to whoever is on the line after the other party hangs up. The sound file simply repeats "The other person has hung up" twice, then hangs up; very similar to how our PSTN lines work in the UK.

Whereabouts can I put this into my FreePBX (or custom) dial plan to work?

Thanks so much

Paul

Statistics : Posted by batteredveg • on Sun Jan 12, 2014 12:15 pm • Replies 1 • Views 32

Remote Phone Stopped Working

$
0
0
Hi everybody Image

I'm having troubles with a phone. We have Cisco spa525G handsets, about 8 of them. All inside the network and two outside but those two are connected through an IPsec tunnel that basically extends the network remotely to that site.

We do have one other phone that is outside the network, and did originally work but then the power went out to the main office where the phone server is, and also to the client house, where the external phone is.

From what the phone configs look like, it seems that it was pointing at the external side of our router and should be pushed to the phone server. However it doesn't seem to be able to. The internet is fine and the phone works on the internal network. I've checked both router configs and they seems fine.

Any help would be greatly appreciated. Just let me know if you need anymore information.

Thanks heaps Image

Daniel

Statistics : Posted by dmoyle • on Sun Jan 12, 2014 5:04 pm • Replies 0 • Views 16

MusicOnHold

$
0
0
Hey vinc, try adding this line to the dialplan;

exten =>n,Set(CHANNEL(musicclass)=you-moh)

Let me know if that works for you Image

Statistics : Posted by vinc • on Fri Jan 10, 2014 5:22 am • Replies 1 • Views 51

MusicOnHold

$
0
0
Hi,
I'm using asterisk 11, I just want to build a call center setup.for that I made custom queue of having only one extension and custom recording for MOH and I put that .wav file in /var/lib/asterisk/mohmp3/vinc.....and I called that in /etc/asterisk/musiconhold.conf..........and called in my queue as music=vinc..............

for testing I made a call, I heard that customised MOH recording in my headset while queue was (ringing voice) ringing, I answered the call. At the same time I jz made another call to that queue to test the waiting tone ....the call was on wait (ringinuse=disabled) and is also playing same MOH with call position and all in Queue.
actually what I want is to separate the 3 instances.

same custom recording for waiting time and Hold time in Queue
and differentiate ringing voice of Queue as default "tring tring" or else.

I tried setmusiconhold in Dialplan .........these 3 instances are getting same MOH.
Is there any possibility to separate these ?????

Thanks in advance ....

Statistics : Posted by vinc • on Fri Jan 10, 2014 5:22 am • Replies 1 • Views 51

WebRTC & Asterisk 11.7.0 - not hear audio

$
0
0
how to good configure ICE in Asterisk?

Statistics : Posted by wacky • on Sun Jan 12, 2014 11:59 am • Replies 10 • Views 193

Multiple calls simultaneously?

$
0
0
We'd like to be able to have one person on their computer be on multiple phone calls at once. Is this something asterisks can do? Some features we'd want.

Calls start/end at different times
Call recordings
Sound and mic for each call separately (can talk on one while the other is muted)
Ideally play audio files (automated responses).

Thanks.

Statistics : Posted by ryandetzel • on Mon Jan 13, 2014 3:26 pm • Replies 0 • Views 19
Viewing all 7460 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>