Skip to main content

Can not dial from Android Connect

Posted by mattdarnell on Fri, 02/02/2018

8.3.1.2 Multi
1.4.1 Connect
Calling using callback

I am trying to place a call from the Android version of Connect and receive the following error in the console:

[2018-02-02 21:19:56] ERROR[1683]: chan_sip.c:17208 register_verify: 'UDP' is not a valid transport for '122-comtel'. we only use 'WS'! ending call.

[2018-02-02 21:19:56] NOTICE[1683]: chan_sip.c:28508 handle_request_register: Registration from '"Matt Darnell" ' failed for '141.239.175.83:5060' - Device not configured to use this transport type

Is there a place to enable wss?

-Matt


Submitted by volodya on Mon, 02/05/2018 Permalink

Hello Matt,

Please check to be sure that there is no SIP phone trying to connect to the system. Also, do you see little green status circle next to your profile icon in the top left corner?

Submitted by mattdarnell on Mon, 02/05/2018 Permalink

Interesting, the SIP phone attempting to register could be causing the error.

Our main use case is people have desk phones and only use the app when they are out of the office. I don't see how we can get users to unplug their desk phone when they want to get calls on the app.

I will test tonight and let you know.

Submitted by volodya on Mon, 02/05/2018 Permalink

Users should not be unplugging their desk phones. Log messages that you sent are not related to the problem with dialing out. Please check if Connect is registered in Asterisk by running "sip show peers" command.

Submitted by eeman on Fri, 03/02/2018 Permalink

after you switch modes to 'use application' do a 'sip show peer XXXX' where XXXX is your exten-tenant to confirm it is showing available. Also how did you make this recording? Knowing this would be very useful for some instructional videos.

Submitted by mattdarnell on Mon, 03/05/2018 Permalink

Erik,

I used team viewer to be able to view the phone on my screen. On top of that I used OBS Studio to record the screen and audio - https://obsproject.com/

-Matt

Submitted by thirdlane on Mon, 03/12/2018 Permalink

Hi Matt,

Are you still experiencing this problem?