Actions
Support #2417
closed
Fail to dial using a Cloudonix Subscriber via "Seacom Outbound Trunk" into Aarenet PBX.
Added by hisky aviv 7 days ago. Updated about 8 hours ago.
Start date:
2025-04-17
Due date:
% Done:
0%
Estimated time:
Session tokens:
4774c36e87a3479d9507ba20e521cd3b
Description
Fail to dial using a Cloudonix Subscriber via "Seacom Outbound Trunk" into Aarenet PBX.
Environment:
Domain: hisky.stg.cloudonix.net
Subscriber: +84678902002
Trunk Name: OutboundTrunk-Seacom is 113.161.141.10:5060 (Aarenet BPX with inbound Trunk).
extension: Zoiper5 configured with 0678902002@hisky.stg.cloudonix.net
Scenario:
Calling number: from Zoiper5 app to +84678902003 of or +84791907968 failing call is rejected.
Cloudonix Log Example:
4774c36e87a3479d9507ba20e521cd3b Call Start Time 2025-03-18 14:05:50.370 UTC.
Errors:
No outbound trunk found to take the call to +84678902003 out of [Seacom outbound Trunk], last status: UNKNOWN
Failed to determine the status of the dial to +84678902003 or +84791907968, and the call is rejected.
Tests: 113.161.141.10:5060 is open and accessible from the Hisky office.
we can make a direct sip call using that PBX.
Files
| sip-trace.log (35.1 KB) sip-trace.log | Oded Arbel, 2025-04-17 15:10 |
Updated by Oded Arbel 7 days ago
- File sip-trace.log sip-trace.log added
Attached SIP trace of specified session
Updated by Oded Arbel 7 days ago
- Status changed from New to Rejected
Aviv, it looks like the IP address 113.161.141.10 is not responsive - as can be seen in the SIP trace, it does not answer any of the INVITE messages our system sends out.
The session you reported is from March 18th - so that's quite a long time ago, but I tried to access the trunk's IP address now - and while it answers PINGs, it does not seem to be responsive to requests on any standard port. There seems to be a major issue with that server, or possibly that it has a very restrictive firewall that has not been configured to allow access from the Cloudonix Platform. As a reminder, in order for trunk configurations to work, the destination server must be able to accept SIP UDP requests from border.cloudonix.io from the source port 5060 to the trunk's specified destination port.
Updated by Oded Arbel about 8 hours ago
Here's an updated trace of session 7d8bcf68767a4c548cd4a421b027ea36 - the last part looks like this:
2025-04-23T13:58:04.797Z 172.24.20.141:5060 -> 113.161.141.10:5060 INVITE sip:+972545442194@113.161.141.10:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 18.219.128.166:5060;branch=z9hG4bKca7d.e6e7c36216b5c5d7b30551c40da933b1.0 Max-Forwards: 69 From: "0678902003" <sip:0678902003@hisky.stg.cloudonix.net>;tag=as0e70dae7 To: <sip:+972545442194@113.161.141.10> Call-ID: 3173e0d810865a164fb5a10937c614e3@3.17.151.111:9067 CSeq: 102 INVITE User-Agent: Cloudonix-App.Core/5.3.177_5.3.591.3_18.23.1 Date: Wed, 23 Apr 2025 13:58:04 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces X-CID: 5a8a201c14364e319e8302bdd0bd9dfc Content-Type: application/sdp Content-Length: 335 TH: dih Contact: <sip:btpsh-67ffb033-3-9f1e@18.219.128.166> v=0 o=root 541481097 541481097 IN IP4 3.142.130.87 s=Asterisk PBX 18.23.1 t=0 0 m=audio 32660 RTP/AVP 0 8 18 101 c=IN IP4 3.142.130.87 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:32661 a=ptime:20 a=maxptime:140 --- 2025-04-23T13:58:05.076Z 113.161.141.10:5060 -> 172.24.20.141:5060 SIP/2.0 401 Unauthorized From: "0678902003"<sip:0678902003@hisky.stg.cloudonix.net>;tag=as0e70dae7 To: <sip:+972545442194@113.161.141.10>;tag=sc2osb1-9fe94acbb9632f6c Call-ID: 3173e0d810865a164fb5a10937c614e3@3.17.151.111:9067 CSeq: 102 INVITE Server: AareSwitch/6.15.13620 Via: SIP/2.0/UDP 18.219.128.166:5060;branch=z9hG4bKca7d.e6e7c36216b5c5d7b30551c40da933b1.0 Contact: <sip:+972545442194@113.161.141.10:5060> WWW-Authenticate: Digest realm="113.161.141.10",nonce="6808f1eca859f890acd34a9b90750b44321ceae2"
Updated by Oded Arbel about 8 hours ago
- Notes #3 changed from Here's an updated trace of session `7d8bcf68767a4c548cd4a421b027ea36` - the last part looks like this:
```
2025-04-23T13:58:04.797Z 172.24.20.141:5060 -> 113.161.141.10:5060
INVITE sip:+972545442194@113.161.141.10:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 18.219.128.166:5060;branch=z9hG4bKca7d.e6e7c36216b5c5d7b30551c40da933b1.0
Max-Forwards: 69
From: "0678902003"
Updated by Oded Arbel about 8 hours ago
Then:
2025-04-23T13:58:05.595Z 172.24.20.141:5060 -> 113.161.141.10:5060 INVITE sip:+972545442194@113.161.141.10:5060;transport=udp SIP/2.0 Via: SIP/2.0/UDP 18.219.128.166:5060;branch=z9hG4bKca7d.e6e7c36216b5c5d7b30551c40da933b1.1 Max-Forwards: 69 From: "0678902003" <sip:0678902003@hisky.stg.cloudonix.net>;tag=as0e70dae7 To: <sip:+972545442194@113.161.141.10> Call-ID: 3173e0d810865a164fb5a10937c614e3@3.17.151.111:9067 CSeq: 102 INVITE User-Agent: Cloudonix-App.Core/5.3.177_5.3.591.3_18.23.1 Date: Wed, 23 Apr 2025 13:58:04 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces X-CID: 5a8a201c14364e319e8302bdd0bd9dfc Content-Type: application/sdp Content-Length: 335 TH: dih Authorization: Digest username="null", realm="113.161.141.10", nonce="6808f1eca859f890acd34a9b90750b44321ceae2", uri="sip:+972545442194@113.161.141.10:5060;transport=udp", response="2fc85d037bde51e76b2b4d46c264bb8d", algorithm=MD5 Contact: <sip:btpsh-67ffb033-5-362e@18.219.128.166> v=0 o=root 541481097 541481097 IN IP4 3.142.130.87 s=Asterisk PBX 18.23.1 t=0 0 m=audio 32660 RTP/AVP 0 8 18 101 c=IN IP4 3.142.130.87 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:32661 a=ptime:20 a=maxptime:140
Actions