• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Call Transfer Failed

Status
Not open for further replies.

giospr

Joined
Aug 26, 2010
Messages
3
Reaction score
0
Hi guys,

I am testing the 3CX ver9 and I have been able to do everything except forward calls to my mobile. I just fixed my initial problem by creating a new outbound rule using my mobile digits, but now I am getting new errors. Could someone give me a hint of what's going on here:

16:55:41.968 [CM503008]: Call(18): Call is terminated
16:55:33.671 [CM503016]: Call(18): Attempt to reach <sip:[email protected]:5060> failed. Reason: Forbidden
16:55:33.671 [CM503003]: Call(18): Call to sip:[email protected]:5060 has failed; Cause: 603 Declined; from IP:209.91.245.5:5060
16:55:31.703 Currently active calls - 1: [18]
16:55:28.921 [CM503003]: Call(18): Call to sip:[email protected] has failed; Cause: 487 Request Terminated; from IP:192.168.1.106:5060
16:55:28.921 [CM503025]: Call(18): Calling VoIPline:0@(Ln.10000@VOZPR - Outgoing Acct)@[Dev:sip:[email protected]:5060]
16:55:28.734 [CM503005]: Call(18): Forwarding: VoIPline:0@(Ln.10000@VOZPR - Outgoing Acct)@[Dev:sip:[email protected]:5060]
16:55:13.734 [CM503025]: Call(18): Calling Ext:Ext.102@[Dev:sip:[email protected]:5060]
16:55:13.671 [CM503004]: Call(18): Route 1: Ext:Ext.102@[Dev:sip:[email protected]:5060]
16:55:13.671 [CM503010]: Making route(s) to <sip:[email protected]:5060>
16:55:08.484 [MS211000] C:18.1: 209.91.245.5:45586 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
16:55:00.046 [CM503007]: Call(18): Device joined: sip:[email protected]:40600;rinstance=67f7ad25eea85719
16:55:00.046 [CM503007]: Call(18): Device joined: sip:[email protected]:5060
16:55:00.046 [CM505001]: Ext.801: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:[email protected]:5060]
16:55:00.046 [CM503002]: Call(18): Alerting sip:[email protected]:40600;rinstance=67f7ad25eea85719
16:54:59.890 [CM503025]: Call(18): Calling Ext:Ext.801@[Dev:sip:[email protected]:40600;rinstance=67f7ad25eea85719]
16:54:59.875 [CM503004]: Call(18): Route 1: Ext:Ext.801@[Dev:sip:[email protected]:40600;rinstance=67f7ad25eea85719]
16:54:59.875 [CM503010]: Making route(s) to <sip:[email protected]:5060>
16:54:59.859 [CM505003]: Provider:[VOZPR - Outgoing Acct] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Sippy] PBX contact: [sip:[email protected]:5060]
16:54:59.859 [CM503001]: Call(18): Incoming call from 17878106280@(Ln.10000@VOZPR - Outgoing Acct) to <sip:[email protected]:5060>
16:54:59.750 [CM503012]: Inbound office hours rule (unnamed) for 10000 forwards to DN:801
 
giospr said:
16:55:33.671 [CM503003]: Call(18): Call to sip:0@sip1.vozpr.com:5060 has failed; Cause: 603 Declined; from IP:209.91.245.5:5060

It looks like you are sending "0" to your provider, and they don't like it.
 
OK. . . I am new to 3CX and not sure how I am doing that. Where should I look in the configuration to fix this?

Thanks for the prompt response!
 
The Outbound rules will be where you specify where (what trunk) and what digits, are sent. An example would be, and this is for North America using a 9 access digit...

Digits would be 9, length would be 11 (9 plus a 10 digit number). you would strip 1 digit (the 9) and prepend (add on) nothing.
If you then dialled 98005551234 the digits 8005551234 would be sent out on the trunk you choose in the rules. If you needed one for long distance you could create a second rule for 91 for 12 digit long numbers. keeping everything else the same you would send out 18005551234 on the trunk. Most VoIP providers in North America want that 1 at the beginning for all calls , local and LD.

You would have to create rules for 411, 611 and other "special" numbers that didn't fall into the other rules, including overseas.
 
Hi leejor,

I took your advice and made modifications to the Outbound Rules and all is working great!!

Thanks a million for your help!! We can finally start testing the 3CX.

Thanks!! :D
 
Status
Not open for further replies.
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.