[bug] App to GSM in PL calls but GSM doesn't ring

[rodrigomonelos]

• [X] Front end changes

• [x] Back end changes

Description: Since about last week Friday or whenever we final got calls from GSM to App to work on SayCel Version there has been a bug not allowing calls to complete to GSM from app Expected result: I Dial 43333 normally not from directory, expect to hear audio greeting and then call to connect Obtained result: I dial 43333 in normal tab not directory, call rings and rings i never hear audio greeting and call does not connect. I understand that the call does not ring on the GSM phone, since Thomas reported this. I tested calling all the numbers in the directory and none of them answered either. Steps to reproduce:

• Open App Dial a number
• tap on green button Call
• listen and hear it rings and rings but does not connect

NOTE Backhaul is working great and when I call from a GSM to App with App open it accepts call normally. Context Device: happens from Samsung J2 Galaxy OS version: Android 5.1.1 Browser: na Other relevant info: … App Version HEAD - c40b696, App has been downloaded and used with much success on this phone before

[gmarcos87]

I get this log:

SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/WSS u1bg8nha00ap.invalid;rport=49346;received=138.255.88.1;branch=z9hG4bK2772716
Max-Forwards: 67
From: "99910038188" <sip:99910038188@rhizortc.specialstories.org>;tag=uobm16ebru
To: <sip:385485876@did.callwithus.com>;tag=ZKygB8Z1UvS8K
Call-ID: evuek3rr9b4moujllhhb
CSeq: 7666 INVITE
User-Agent: CWU SIP GW
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Length: 0

Perhaps some of our specialists in sip or kamailio can understand better what is happening. I know it has to do with the particular configuration of saycel.

[rodrigomonelos]

Agreed that @gmarcos87 will change code on the app so calls not go through CallWithUs anymore (will be CallWithSomeoneElse now)

[gmarcos87]

What do I do with this then? Apparently it was a callwithus problem. As soon as the changes are ready in the backend to remove that gatewey can be done quickly. I suppose then the numbers are going to have to be complete (eleven digits) and not only the 5 that saycel uses now.

[rodrigomonelos]

Go on, Edwin asked to make the change. Please share a message in the group after you changed it including your comments on what might be needed to change on the rest of the system in case they are useful for Dhruv, Edwin, Thomas or who will be in charge of making the changes. Thanks

2017-10-20 11:47 GMT-04:00 Marcos Gutierrez notifications@github.com:

What do I do with this then? Apparently it was a callwithus problem. As soon as the changes are ready in the backend to remove that gatewey can be done quickly. I suppose then the numbers are going to have to be complete (eleven digits) and not only the 5 that sayex uses now.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/saycel/webph.one/issues/102#issuecomment-338245206, or mute the thread https://github.com/notifications/unsubscribe-auth/AZmH3s0D_vmpkCDN8kBtnMccqNQ5wd6_ks5suMCFgaJpZM4P9625 .

--

Ing. Rodrigo Monelos [image: https://]about.me/rodrigo.monelos https://about.me/rodrigo.monelos?promo=email_sig

[gmarcos87]

Close?