Incoming Fine outgoing not working

[Foggy]

Struggling to get outgoing working attached my outbound rules from UK And the entry in the logs. 11/07/2019 9:03:48 AM - Leg L:10.1[Extn:000] is terminated: Cause: BYE from PBX

11/07/2019 9:03:48 AM - Terminated from "Dewhurst, Tony"<sip:[email protected]>;tag=c8475248 to <sip:[email protected]:5060>;tag=6c8c0f5f; reason: Rejected

11/07/2019 9:03:48 AM - L:10.1[Extn:000] Sending: OnSendResp Send 404/INVITE from 0.0.0.0:0 tid=5eee9b140719bb07 Call-ID=aRqWxdpwFIrRigcxNUTO5w..: SIP/2.0 404 Not Found Via: SIP/2.0/UDP 127.0.0.1:5063;branch=z9hG4bK-524287-1---5eee9b140719bb07;rport=5063 To: <sip:[email protected]:5060>;tag=6c8c0f5f From: "Dewhurst, Tony"<sip:[email protected]>;tag=c8475248 Call-ID: aRqWxdpwFIrRigcxNUTO5w.. CSeq: 2 INVITE Warning: 499 ip-172-31-31-72.eu-west-2.compute.internal "Not found" Content-Length: 0

 

[AWS2P]

try to move up rule uk national before international

Do you have log in verbose?

 

[Foggy]

try to move up rule uk national before international

Just tried that still fails.

 

[AWS2P]

your test call was from ext 000 to 441772432055 ?
If so 44 is not defined in your rules , your setting is UK numbers starting with 0 so rule can't match

 

[Foggy]

Yes was from 000 so tried stripping the +44 so dialled 01772432055 and theses are the logs I received from failed call.

11/07/2019 9:31:49 AM - Leg L:15.1[Extn:000] is terminated: Cause: BYE from PBX

11/07/2019 9:31:49 AM - Terminated from "Dewhurst, Tony"<sip:[email protected]>;tag=df2a7937 to <sip:[email protected]:5060>;tag=9a083327; reason: Rejected

11/07/2019 9:31:49 AM - L:15.1[Extn:000] Sending: OnSendResp Send 404/INVITE from 0.0.0.0:0 tid=32339c1c31a36b00 Call-ID=dVee3_AXozGDKYrxJ8kkHQ..: SIP/2.0 404 Not Found Via: SIP/2.0/UDP 127.0.0.1:5063;branch=z9hG4bK-524287-1---32339c1c31a36b00;rport=5063 To: <sip:[email protected]:5060>;tag=9a083327 From: "Dewhurst, Tony"<sip:[email protected]>;tag=df2a7937 Call-ID: dVee3_AXozGDKYrxJ8kkHQ.. CSeq: 2 INVITE Warning: 499 ip-172-31-31-72.eu-west-2.compute.internal "Not found" Content-Length: 0

11/07/2019 9:31:49 AM - SendMsg from <sip:[email protected]:5060>;tag=9a083327 to "Dewhurst, Tony"<sip:[email protected]>;tag=df2a7937

11/07/2019 9:31:49 AM - ~Target=Unknown:01772432055@(Ln.10000@Generic SIP Trunk)

11/07/2019 9:31:49 AM - Call(C:15) is terminated

11/07/2019 9:31:49 AM - [CM503020]: Call(C:15): Normal call termination. Call originator: Extn:000. Reason: Not found

11/07/2019 9:31:49 AM - [CM503016]: Call(C:15): Attempt to reach <sip:[email protected]:5060> from Extn:000 has failed. Reason: Not Found

11/07/2019 9:31:49 AM - [Flow] Current call diversion path:[]

 

[AWS2P]

If i was you, as your rules are only granting access out everywhere so simplest way should be to set only one rule with Default group criteria (extensions need to belong default group of course)

 

[Foggy]

Any chance you can tell me what to put its doing my head in

 

[AWS2P]

here is course about outbound rules
https://www.3cx.com/docs/manual/sip-trunks/#h.3evqdta9sabf

try this rule alone
https://www.3cx.com/community/threa...s-not-found-inbound-is-fine.69198/post-303290

 

[Foggy]

I think this could be network related as we have a public ip and a private in aws when we make an outgoing call I see it tagged as the private see the attached pic (fails not on SIP whitelist)


But when I make a succesfull inbound call I see it tagged differently.



The sip works on a single allowed IP 3.8.133.177

 

[AWS2P]

OK, as we didn't start from the begining, can you please provide more details answering this:

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/
:

1. Is it a new install never working fine?
2. Is it a running one recently being with this problem ?

 

[Foggy]

• 3CX Version
  

  16.0.676

• Server OS, Debian from PBX express install
• IP Phone Make/Model/Firmware Softphone
• Provisioning Method: Local / VPN / STUN / SBC
• Trunk Provider or Gateway Make/Model Colt
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

Brand new install

OK, as we didn't start from the begining, can you please provide more details answering this:

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/
:

1. Is it a new install never working fine?
2. Is it a running one recently being with this problem ?

 

[AWS2P]

you have only softphones?
PBx is cloud hosted? on premise?
Do you use 3CX FQDN or your own ?

 

[Foggy]

Found the issue in the wiretrace it was down to the + being stripped off the callerID

Thank you aws2p this is for a mini proof of concept so just softphone for time being.

 

[Alphabetic]

Why not configure the E.164 under Settings > E164?

 

[Foggy]

I did do the above but that was what was stripping the numbers the SIP wanted +44 so now I have just a rule stripping the 0 and appending the +44 now it works fine.

I had to disable the e164 handling

 

[AWS2P]

Glad you found alone real cause

 

[MH-Nottingham]

Can you upload a screenshot or step by step of how you fixed this, please?

 

[Foggy]

All I did was add a + to the caller ID field in the extension users. but I discovered the issue from doing a PCAP trace from the log view.

And then drilling in to the results using wireshark I discovered this...