Solved 3CX Lightsail Cloud No outbound on any clients

Status
Not open for further replies.

Rodney Manning

Silver Partner
Basic Certified
Joined
Jan 9, 2019
Messages
6
Reaction score
0
I have searched all the threads and googled the devil out of this problem and have had no luck in fising the problem. Here is a copy of the log file for a particular call that gets the 604 error.

Code:
01/09/2019 7:54:35 AM - Leg L:147.1[Extn:2001] is terminated: Cause: BYE from PBX
01/09/2019 7:54:35 AM - [CM503020]: Call(C:147): Normal call termination. Call originator: Extn:2001. Reason: Not found
01/09/2019 7:54:35 AM - L:147.1[Extn:2001] failed to reach Line:10000>>5733805908, reason Not Found
01/09/2019 7:54:35 AM - Leg L:147.2[Line:10000>>5733805908] is terminated: Cause: 604 Does not exist anywhere/INVITE from 67.103.60.107:5060
01/09/2019 7:54:35 AM - Call to T:Line:10000>>5733805908@[Dev:sip:[email protected]:5060] from L:147.1[Extn:2001] failed, cause: Cause: 604 Does not exist anywhere/INVITE from 67.103.60.107:5060
01/09/2019 7:54:35 AM - [CM503003]: Call(C:147): Call to <sip:[email protected]:5060> has failed; Cause: 604 Does not exist anywhere/INVITE from 67.103.60.107:5060
01/09/2019 7:54:35 AM - [CM503025]: Call(C:147): Calling T:Line:10000>>5733805908@[Dev:sip:[email protected]:5060] for L:147.1[Extn:2001]
01/09/2019 7:54:35 AM - [CM503027]: Call(C:147): From: Extn:2001 ("Rodney Manning" <sip:[email protected]:5060>) to T:Line:10000>>5733805908@[Dev:sip:[email protected]:5060]
01/09/2019 7:54:35 AM - [CM503004]: Call(C:147): Route 1: from L:147.1[Extn:2001] to T:Line:10000>>5733805908@[Dev:sip:[email protected]:5060]
01/09/2019 7:54:35 AM - Line limit check: Current # of calls for line Lc:10000(@Megapath[<sip:[email protected]:5060>]) is 0; limit is 2
01/09/2019 7:54:35 AM - Call(C:147): Call from Extn:2001 to 5733805908 matches outbound rule 'SI Outbound'
01/09/2019 7:54:35 AM - [Flow] Call(C:147): has built target endpoint: Out#:>>Rule{SI Outbound}>>5733805908 for call from L:147.1[Extn:2001]
01/09/2019 7:54:35 AM - [Flow] Target endpoint for 5733805908 is Out#:>>Rule{SI Outbound}>>5733805908
01/09/2019 7:54:35 AM - [CM503010]: Call(C:147): Making route(s) from Extn:2001 to <sip:[email protected]:5060>
01/09/2019 7:54:35 AM - [CM505001]: Endpoint Extn:2001: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXP2170 1.0.9.102 000b8292ea6c] PBX contact: [sip:[email protected]:5060]
01/09/2019 7:54:35 AM - [CM500002]: Call(C:147): Info on incoming INVITE from Extn:2001: Invite-IN Recv Req INVITE from 75.130.221.237:5065 tid=2118546662 [email protected]: INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 75.130.221.237:5065;branch=z9hG4bK2118546662;rport=5065 Max-Forwards: 70 Contact: "Rodney Manning" <sip:[email protected]:5065> To: <sip:[email protected]> From: "Rodney Manning"<sip:[email protected]>;tag=1125407809 Call-ID: [email protected] CSeq: 71 INVITE Accept: application/sdp, application/dtmf-relay Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE Content-Type: application/sdp Proxy-Authorization: Digest username="xV9znMASrc",realm="3CXPhoneSystem",nonce="414d53595c35fd1b08:79360b4eb3369daa0109711c54079195",uri="sip:[email protected]",response="71a4b3d181707642c023e56fcd1b439f",algorithm=MD5 Supported: replaces, path, timer User-Agent: Grandstream GXP2170 1.0.9.102 000b8292ea6c Privacy: none P-Preferred-Identity: "Rodney Manning" <sip:[email protected]> P-Emergency-Info: IEEE-EUI-48;eui-48-addr=00-0B-82-92-EA-6C Content-Length: 342 v=0 o=2001 8000 8000 IN IP4 75.130.221.237 s=SIP Call c=IN IP4 75.130.221.237 t=0 0 m=audio 14012 RTP/AVP 0 8 9 18 123 101 a=sendrecv a=rtpmap:0 PCMU/8000 a=ptime:20 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:123 opus/48000/2 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15
01/09/2019 7:54:35 AM - [CM503001]: Call(C:147): Incoming call from Extn:2001 to <sip:[email protected]:5060>
 
Hello @Rodney Manning

I would recommend contacting your provider regarding this issue as it seems that the 604 error is originating from them. Perhaps the format you are using to place calls is not correct or your outbound parameters need adjusting. In either case this is something your provider will be able to help you with.
 
Glad to see the issue has been resolved and thank you for updating the thread with your solution
 
Status
Not open for further replies.

Forum statistics

Threads
111,910
Messages
589,690
Members
164,775
Latest member
Chester McTester