similar to: Letting rtp profiles be handled by rtpengine instead of Asterisk

Hello, I noticed a strange thing while testing my Asterisk-Kamailio Realtime setup. In an INVITE the From and To headers contain the same number when calling through a Realtime integration setup. This happens when the INVITE leaves Asterisk. Can you guys tell me what might be causing this? I have 660 at testers.com as a websocket client and 700 at testers.com (caller) using a Zoiper client (db

Greetings, I've noticed a problem that might originate from my Asterisk configuration, could use a hand in sorting it out. Problem is a 488 response from Asterisk whenever it gets RTP/SAVPF profile in the SDP. My current setup has Asterisk Kamailio realtime integration, and Kamailio uses dispatcher to route calls for Asterisk to handle. Now I have only one Asterisk, on the same machine as

Hello, I'd appreciate your comments on the following problem I'm having, please forgive me if this is something obvious, I've been scratching my head on this for a while: I have Asterisk+Kamailio setup where I'm currently testing inbound calls from outside. I have both webrtc and sip clients, where webrtc peers are defined according to sip.js instructions (

Hello, I have a problem with a call between 2 webrtc clients. Asterisk removes the ice-related lines from the sdp when it sends the INVITE out, and the called webrtc client rejects the INVITE due to the missing ice lines. Both webrtc clients are defined exactly the same way, same values in all fields except the number of the peer. There's probably something I've changed that causes this

For those that were interested I have attached the kamailio.cfg which we have working with Kamailio 4.2.1 and Asterisk 1.8.23/32. Specifically, the following yum packages: kamailio.x86_64 4.2.1-4.1 @home_kamailio_v4.2.x-rpms kamailio-auth-ephemeral.x86_64 4.2.1-4.1 @home_kamailio_v4.2.x-rpms kamailio-bdb.x86_64 4.2.1-4.1 @home_kamailio_v4.2.x-rpms

Can anyone recommend a good WebRTC phone to use with Asterisk? I do not mind if it is commercial or open source. Customers are starting to ask for web solutions and we need to start testing. -- Telecomunicaciones Abiertas de M?xico S.A. de C.V. Carlos Ch?vez +52 (55)9116-91161

I'm having the same issue! The difference in my case is Asterisk server has a public IPv4 and the browser is behind a single NAT. I'm forwarding my configuration below (which I posted previously on asterisk-users). How can we debug ICE negotiation? ---------- Forwarded message ---------- From: Vinicius Fontes <vinicius at aittelecom.com.br> Date: 2015-07-27 13:54 GMT-03:00

I think your phone may be trying to register with the username '1234', while your sip configuration is expecting 'luca'. Can you try changing your phone registration credentials to use 'luca'? Can you give us a sip transcript when you try to place a call from it? On 15-05-28 05:09 PM, Luca Bertoncello wrote: > Darryl Moore <darryl at moores.ca> schrieb: >

Hi All, I have configured WebRTC according to the install document. The clients register correctly. I'm use SIPjs. The clients are able to send messages to the server. The SIP debug shows the messages being received. However I'm stumped for directions on how to route the messages between the clients. Asterisk 11.11.0 Here is my client sip config: [1060] type=friend username=1060 ; The

Hi list! Finally I got my wife's phone working in my Asterisk. Unfortunately I have some problems, too... Current situation: - AsteriskNOW with 4 Accounts (00493511111111, 00493512222222, 00493513333333, 5678). This is "for test" and it will be replaced by "the real world", when I got my Asterisk to work... - A second Asterisk (Ubuntu-PBX) on another VM, logging in

Hello all, I've been testing a Kamailio Asterisk Realtime integration, and found a strange situation. My problem is that when using the integration, everything seems ok but Asterisk does not see the clients as registered. Kamailio and the clients report registered clients. Also calls fail. In Asterisk cli sip show peers shows nothing but for example realtime load sipusers name 660 shows the

Darryl Moore <darryl at moores.ca> schrieb: > Ahh. Seen that before! That suggests to me that you don't have your > sip.conf records setup right. > > What's your sip.conf look like? Well, here what I wrote in my sip.conf: register => 00493511111111:MYSECRET at pbxluca/00493511111111 register => 00493512222222:MYSECRET at pbxfax/00493512222222 register =>

Hi I'm attempting to use ICE to be able to present all possible RTP transports to peers. 16.28.0~dfsg-0+deb11u2 (I know it's old, but unfortunately Asterisk was removed from debian 'stable' and the version in 'sid' is just broken (opus + voicemail don't work anymore). But I ran into an issue when the peer is running rtpengine: Asterisk offers: a=candidate:H9da13901

On Wed, Mar 4, 2015 at 12:47 AM, Jarrod Cuzens <jarrod at mogl.com> wrote: > For those that were interested I have attached the kamailio.cfg which we > have working with Kamailio 4.2.1 and Asterisk 1.8.23/32. Specifically, the > following yum packages: > > kamailio.x86_64 4.2.1-4.1 > @home_kamailio_v4.2.x-rpms > kamailio-auth-ephemeral.x86_64

I am using Asterisk 11.3.0 and just updated Nightly to 24.0a1 (2013-06017) and get a SIP 488 Not Acceptable Here response. I have no problems using the same Asterisk configuration and the same page to make a call from Chrome. I have seen other people post a similar issue, but I have not seen a solution. If someone with good knowledge of this issue were to respond with "this is a known

For the client: JSSIP and Sipml5. If you are going to be coding something up yourself I like the JSSIP 0.5.x javascript interfaces. If you are simply going to use a pre-canned one then sipml5 works pretty well and remembers your settings in localstorage. I haven't used any closed source versions since the above works really well for us. For the server: If you are using Asterisk 1.8

I am having trouble getting Google Chrome to accept a WebRTC call coming from Asterisk, even though Firefox can (now) accept the same call without issue. My setup is as follows: Server: CentOS 7 x86_64 (Elastix 4 RC) with IP: 10.1.0.4 192.168.5.146 asterisk-11.21.0 patched to work around https://issues.asterisk.org/jira/browse/ASTERISK-25659 openssl-1.0.1e-51.el7_2.2.x86_64 [root at elx4 ~]#

Am 03.03.2015 um 18:16 schrieb James B. Byrne: > CentOS-6.5 (FreePBX-2.6) > Asterisk-11.14.2 (FreePBX) > snom870-SIP 8.7.3.25.5 > > I am having a very difficult time attempting to get TLS and SRTP > working with Asterisk and anything else. At the moment I am trying to > get TLS functioning with our Snom870 desk-sets. And I am not having > much luck. > > Since this

Hi again, list! I know, I'm really annoying the list... :) Well, maybe I got my Asterisk at home ("wrt" on the previous E-Mails) to accept my mobile phone from Internet. It was a problem with the network and the firewall. Now I can log my mobile phone in my Asterisk in and the phone is REACHABLE. Wow! Got it! If I call a phone at home using my cellphone it works and the

> > Asterisk needs urgently to push the RTP engine to the Kernel, away from > userland, like professional and commercial softwares do. I measured the > cost of passing call from a public IP to a private IP, like typically a > Session Border Controller may do. In Asterisk, ulaw, no transcoding, it > takes 1.7% of a 3 Ghz core. If the packets where flowing through the > kernel,