Top

Calls problem - JingleSession.prototype.createdOffer failed: TypeError: adapter.default is undefined

Kommentare

13 Kommentare

  • Andreas HEISE

    Hello Jesus,

    please test with the latest SDK version 1.56.1. If the problem persists you should post your question in the Hub Support Community which is the right board for developer questions.

    brgds

    Andreas

    0
    Aktionen für Kommentare Permalink
  • Louise QUINTRAND

    Hello Jesùs :)

    I'm gonna upload your post to the Hub Support Community so that it is in the right place to get as many relevant answers as possible:) 
    You can see your post right here https://support.openrainbow.com/hc/en-us/community/posts/360004005060-Calls-problem-JingleSession-prototype-createdOffer-failed-TypeError-adapter-default-is-undefined. 

    0
    Aktionen für Kommentare Permalink
  • Jesús Giménez

    Thanks all, my problem is still there. I have two apps in angular 7, one with routing and lazy loading and another one without it. Only the app without lazy loading works, I think the lazy loading conflict with calls but i don't know why.

    I have to store some global data in app to be able to establish webRTC call?

    When i go to call's module and make the call, it throw me this errors, think could be for that (lazy loading remove some scope variables needed?).

    Any idea? Thanks!

    0
    Aktionen für Kommentare Permalink
  • Konrad Hyzy

    Hi,

     

    have you tried updating the SDK version to the newest one? 

     

    Konrad

    0
    Aktionen für Kommentare Permalink
  • Jesús Giménez

    Hi, yes I updated and still the same:

    Wed Jun 12 2019 10:49:08 | RBW-SDK | SDKSrv | [initialize ] :: Version SDK | 1.56.1

    [Strophe.jingle] JingleSession.prototype.createdOffer failed: TypeError: adapter.default is undefined

     

    Edit: testing more with this proyect I deleted lazy loading and still not working, now the only difference between the app working and not is the Routing and SDK Version (same code, components, services, etc...). I'm using Angular 7 and need routing to build more complex apps, any help please?

     

    Thanks in advance!

     

    0
    Aktionen für Kommentare Permalink
  • Jesús Giménez

    Hello another time,

     

    New error related to the last, i put all the rainbow calls inside component and still happen same problem. Maybe I have to do something to work with routes and calls? I lost reference to some objects?

    [Strophe.jingle] JingleSession.prototype.createdOffer failed: TypeError: Cannot read property 'browserDetails' of undefined

     

    Thanks in advance!

    0
    Aktionen für Kommentare Permalink
  • Konrad Hyzy

    Hi, I tried to reproduce your problem but couldn't create the error in my application.

    Would you be able to share your code with me so I can have a look? 

    (although I will take one last shot: what AngularJS version do you load in your HTML script tag?) 

     

    Best Regards,

    KH

    0
    Aktionen für Kommentare Permalink
  • Jesús Giménez

    Hello Konrad,

     

    I'm using AngularJS 1.7.5 as says in documentation with RB version more than 1.53.

    I can share code but think its easier to send the files in private message (160kb without node_modules).

    This app is more complex than others I made, with routing, calls service, popup listening for calls. Little bit difficult to debug here.

    Basic scenario is:

    -Login to rainbow and redirect to main route

    -Navigate to calls route

    -Select contact and call with button

    -Button calls:

    llamar(contact): void {
    this.cs.llamar(contact);
    }

     

    cs is the calls service:


    llamar(contact) {
    rainbowSDK.webRTC.callInAudio(contact);
    }

     

    Call gets connecting but stay there and throw above errors.

    If you want, as I said, I can share the full code.

     

    Thanks.

    0
    Aktionen für Kommentare Permalink
  • Konrad Hyzy

    Hi,

     

    would you be able to share the code with me by email?

     

    konrad.hyzy [at] al-enterprise[dot]com

     

    Thanks,

    KH

    0
    Aktionen für Kommentare Permalink
  • Konrad Hyzy

    Hi again,

     

    I think the problem is related to the fact that Rainbow Web SDK doesn't find the HTML elements necessary to make the call on the very moment when the function is being called. You need to make sure that those tags are exposed in the DOM structure by the application (in this case it's Angular).

    Rainbow Web SDK heavily relies on them so far and it is really necessary to use the same ID parameters as provided in the documentation. 

    Konrad

    0
    Aktionen für Kommentare Permalink
  • Jesús Giménez

    Thanks Konrad,

     

    I re-check and always globalAudioTag stay visible in DOM (with display=none). I have all correct references and call response object say OK. When I make the call, it stay connecting and throw same error:

    Cannot read property 'browserDetails' of undefined

    If I add the video tags still the same.

     

    I don't know what to do since this browserDetails come from Rainbow servers.

     

    Thanks,

    regards!

    0
    Aktionen für Kommentare Permalink
  • Konrad Hyzy

    Hi,

    the problem comes from the fact that the scripts are not loaded by the application in the correct order. Make sure your main HTML document has the scripts loaded in the way presented in our documentation.

     

    Warm Regards,

    Konrad Hyzy

    0
    Aktionen für Kommentare Permalink
  • Jesús Giménez

    Thanks Konrad!! It's solved. 

    Just delete importing scripts from angular.json and moved to index.html. 

     

    0
    Aktionen für Kommentare Permalink

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Sie können immer noch nicht finden, was Sie brauchen?

  • Kontaktieren Sie uns

    Haben Sie eine Frage zu Rainbow? Hinterlassen Sie uns eine Nachricht, um weitere Informationen zu erhalten.

    Kontakt
  • Fragen Sie die Gemeinschaft

    Brauchen Sie Hilfe? Stellen Sie Ihre Fragen in der Community, um Antworten von anderen Rainbow-Benutzern zu erhalten.

    Nachricht posten