External Calls getting a "Called failed" for all Android and Iphone apps

[jonathanarcher]

Seen several threads with similar problems, but no solution that seems to work. It appears every single iPhone or Android with the app in my organization gets a "called failed" when from an external call. Internal calls work fine. The desktop app works fine.

Output logs from one of the phones is below. The logs for other phones appear have the same errors.

13:13:55.240 pjsua_call.c Unable to make call: Invalid Request URI (PJSIP_EINVALIDREQURI) [status=171042]
13:17:10.983 pjsua_call.c Unable to make call: Invalid Request URI (PJSIP_EINVALIDREQURI) [status=171042]
13:18:03.225 [2015568] VERBOSE MODE CHANGED:true
13:18:04.777 [2015628] [statuses] - isLastFirst: true
13:18:14.974 [2015627] myphone.MyPhone_Notifications_RequestCallHistory:
CallType: AllCalls
DnOwner: "123"
RecordLimit: 128
RecordOffset: 0

13:18:19.328 [2015570] [APP] received VOIP push
13:18:19.328 [2015570] sceneActive: true, noCalls: false, backgroundTaskActive: false
13:18:19.328 [2015570] [Lifecycle] - Lifecycle Task start ignored, app not in background
13:18:19.370 [2015627] Ringing call dnzHBRHyW8SO9fB3vlXHCw..02155d600 has connection
13:18:19.370 [2015627] Lifecycle] - Ringing calls: true
13:18:19.370 [2015627] [Lifecycle] - calls updated, sceneActive: true, noCalls: false, backgroundTaskActive: false
13:18:19.370 [2015627] CallKit presented the incoming call
13:18:19.370 [2015627] Ringing call dnzHBRHyW8SO9fB3vlXHCw..02155d600 has connection
13:18:19.370 [2015627] Ringing call dnzHBRHyW8SO9fB3vlXHCw..02155d600 has connection
13:18:19.370 [2015627] Ringing call dnzHBRHyW8SO9fB3vlXHCw..02155d600 has connection
13:18:19.370 [2015627] Calls: [<CXCall: 0x282c27c20>]
13:18:21.676 [2015627] <CXAnswerCallAction 0x2807bc690 UUID=3D3D1B3A-9E3E-4259-8882-C5C22C34C34E state=0 commitDate=2022-08-23 17:18:21 +0000 callUUID=53F125BE-4C39-407F-ABF7-F57CE4FA4EA6 localLandscapeAspectRatio={0, 0} localPortraitAspectRatio={0, 0} dateConnected=(null) downgradeToAudio=0 pauseVideoToStart=1>
13:18:21.678 VCE|PjsipCall in setListener() for call -1
13:18:21.678 VCE|Timer Scheduling timer 105 in 0 ms, id = 0x2807fc4d0
13:18:21.678 VCE|Timer Scheduling timer 105 as first
13:18:21.678 VCE|PjsipCall ***************** CREATING OUTGOING CALL TO (XXX) XXX-XXXX, cl = 0, this = 0x10933b8c0
13:18:21.678 VCE|Timer Scheduling timer 106 in 0 ms, id = 0x2807fd650
13:18:21.678 VCE|Timer Put new timer 106 to the heap
13:18:21.678 VCE|CallSet Create CallSet 0x2815e8ef8 with listener 0x0
13:18:21.678 VCE|PjsipCall in setListener() for call -1
13:18:21.678 VCE|Timer Scheduling timer 107 in 0 ms, id = 0x2807ffc60
13:18:21.678 VCE|Timer Put new timer 107 to the heap
13:18:21.689 VCE|PjsipCall in scheduled setListener() for call -1
13:18:21.689 VCE|PjsipCall ***************** CREATING OUTGOING CALL SIP URI = <sipXXX) [email protected];tag3cx=cjtpyeef>
13:18:21.689 pjsua_call.c Making call with acc #0 to <sipXXX) [email protected];tag3cx=cjtpyeef>
13:18:21.689 pjsua_aud.c Set sound device: capture=-99, playback=-99
13:18:21.689 pjsua_aud.c Setting null sound device..
13:18:21.689 VCE|PjsuaCallbacks ************************ on_snd_dev_operation 1
13:18:21.689 pjsua_aud.c Opening null sound device..
13:18:21.689 pjsua_call.c Unable to make call: Invalid Request URI (PJSIP_EINVALIDREQURI) [status=171042]
13:18:21.689 pjsua_media.c Call 1: deinitializing media..
13:18:21.689 VCE|Timer Scheduling timer 108 in 0 ms, id = 0x28079dd50
13:18:21.689 VCE|Timer Put new timer 108 to the heap
13:18:21.689 VCE|PjsipCall in scheduled setListener() for call -1
13:18:21.689 VCE|CallSet CallSet: *********** RequestFailed **** type = 0, code=0, call -1 0x10933b8c0 0x10933b8c0
13:18:21.689 pjsua_aud.c Closing sound device after idle for 0 second(s)
13:18:21.689 VCE|PjsuaCallbacks ************************ on_snd_dev_operation 0
13:18:21.689 pjsua_aud.c Closing null sound device..
13:18:21.791 [2015570] CallCommand(call: <ICall: 0x2807fee60>, command: _cxphone.SipNotification.requestFailed, requestFailed: Optional(<RequestFailedEvent: 0x28079cd20>))
13:18:21.791 [2015570] Lifecycle] - Ringing calls: false
13:18:21.792 [2015570] [Lifecycle] - calls updated, sceneActive: true, noCalls: true, backgroundTaskActive: false
13:18:21.792 [2015570] Dialer: Request failed
13:18:21.812 [2015570] Calls: []
13:18:21.812 [2015570] Calls: []
13:18:24.793 [2015627] Dialer:
13:18:28.783 [2015570] Ignored notification to be displayed in foreground
13:18:30.431 [2015568] [statuses] - isLastFirst: true

 

[Vali_3CX]

I see this:
<sip: (XXX) [email protected];tag3cx=cjtpyeef>
What are those "()"?

 

[jonathanarcher]

We are using the SalesforceV2 Integration. Our marketing department has all our numbers stored in Salesforce in (xxx) - xxx -xxx format. I had the below Reformat Inbound rule to match our Salesforce.

Source Pattern
(1)(...)(...)(....)

Replace Pattern
(\2) \3-\4

I assumed by your comment the mobile apps don't like the "(" character, so I temporarily removed the reformat rule. Sure enough everybody is working fine now on all phones, iPhone and Android.

Am I correct in assuming it is the "(" character that is messing with the mobile apps? Is there any other work around to this, or going to be fixed in a future release?

 

[Vali_3CX]

Yes, you're correct, that's what I was referring to, the brackets are not accepted by the client's SIP engine (PJSIP_EINVALIDREQURI means "Error, invalid request URI") To be convinced, try on your iPhone native phone to dial such number, and you will see you cannot. So there's no workaround apart from properly configure the PBX, as you already did.

 

[jonathanarcher]

Understood. I am already working with our Marketing to update the format. I am curious though, calls where still coming in on the desktop app. What is the difference there?

 

[Vali_3CX]

Yes. Desktop app and WebClient are both SIP connected, so they answer to a SIP INVITE. Unlike them, the mobile clients are using PUSH, so technically they don't answer, they make a SIP call (with replaces) to the destination (caller-id) specified in the PUSH payload - and that should be in the correct/allowed format.

 

[jonathanarcher]

I see. Makes sense. Thank you for all your help.