SIP Trunk with minimal Information

kanuns · October 2, 2022, 9:50pm

Hi,

I hope you people are doing well.
I have been doing this since long but today i am facing a very tough situation. I have to configure a SIP trunk with very minimal information. And on top of that, I am not able to get any help from the provider (i feel I made a mistake but there is none available in that remote area)

The SIP Trunk provider is using Huawei SE2980

The above is the online information I have received (and the Outbound CID)

I am 100% clueless on how to set this up. Can any “PLEASE”, “PLEASE” guide me to any manual or help me in this.

My Asterisk version is 16. Im using Freebpx.

Again, please help.

david55 · October 2, 2022, 10:48pm

The documentation for this is for customers and partners only, so knowing the device isn’t very helpful.

This is on a private network. Please explain the topology.

Are they supplying this gateway?

Please explain why they think they control this. It implies that you have no control over IP of the FreePBX system. Are they providing DHCP to achieve this?

Stating the obvious. No real information. Should not be taken as a contraindication for using chan_pjsip.

Router setting, not really relevant.

Default

Voice quality claim, not something you can control. A score of up to 3.1 counts as “Nearly all users dissatisfied”, so this is more a lack of quality claim!

Looks like you need to make sure that your FreePBX machine has the IP address they specify, and an appropriate default route for their gateway. Otherwise, it looks like a simple, no authentication, no registration (IP authentication) configuration.

kanuns · October 2, 2022, 11:00pm

Ok, ill tell in detail.

Yes this is a private IP. I have my own IP of my freepbx. they give me another LAN (via fiber) which I connected to my another lanport of freepbx.

Yes, they have given me this gateway.

I do have control on my freepbx, as I informed above, they have given me a static IP via fiber and these IPs are accessible via that gateway.

I have never configured this “simple” config where the signaling and media IPs are different. I need guidance. Please. im stuck.

david55 · October 2, 2022, 11:16pm

You only configure the signalling IP. The media IP is specified by them in their SDP, and the only relevance to you is that you must not block it in your firewall.

kanuns · October 2, 2022, 11:39pm

Please check, this is the setting I have done. (which does nothing. I am sure I am missing somethings).

Stewart1 · October 3, 2022, 12:12am

Is this an existing production system? If not, please use a current FreePBX version (15 or 16) and set up a pjsip trunk.

If it is in production, please describe the networking setup (do you have multiple network interfaces, what kinds of trunks do you have, etc.).

kanuns · October 3, 2022, 10:17am

Yes, this is an existing production system.

Yes I have 2 interfaces. One is used to manage Freepbx and the other is used to connect SIP trunk with the provider.

Following is the IP they have given me:
|Service IP address (Customer)|Signaling: 10.66.200.158 and Media: 10.66.200.158|
|Service IP address : Signaling: 10.66.125.126 and Media: 10.74.123.124|

My IP with which I access Freepbx is 192.168.200.10

david55 · October 3, 2022, 10:41am

This is invalid. The correct delimiter is comma. Also, it is, at least advisable to have disallow=all, or !all as the first “codec”, although maybe FreePBX sets this in the general section.

Also you have ulaw, but they say they only support A-law. This should be harmless. Unless there is some reason you really want G.729, you should not include that.

The other thing you need to do is to provide logging. At least the basic logging described in Providing Great Debug - Support Services - Documentation but you probably also need to use the CLI command “sip set debug on” before capturing this.

kanuns · October 3, 2022, 10:55am

I have removed and only allowed the alaw.
besides that, is everything ok?
have I written the host (the signaling server) correct? I mean signaling should be host right?

And, should I put anything in the incoming settings ?

david55 · October 3, 2022, 11:02am

disallow=all needs to be included somewhere, either FreePBX does it, or you have to do it. Doing it redundantly won’t cause any harm.

host is correct.

You don’t need an inbound section as it is the same as the outbound section (if the outbound section were really only for outbound, the context would be redundant).

kanuns · October 3, 2022, 11:06am

I have already done that (thanks to your last msg)

This is the setting i have done.

type=peer
disallow=all
allow=alaw
protocol=udp
dtmfmode=rfc2833
context=from-trunk
host=10.66.194.136

Please guide if this is all what is needed. (yes they have changed the IP which is not replying to ping at the moment) but is that all ?

david55 · October 3, 2022, 11:13am

That’s all until you provide some logging that contradicts the simplest interpretation of what they have told you.

You’ll obviously need inbound routes, for which you will need to know how they present the “DID”. If they don’t tell you, logging will be the easiest way of getting the answer.

kanuns · October 3, 2022, 11:18am

I am in contact with them. I need to get the ping reply from the signaling server. As soon as I get that, I will log the logs and reply back.
by the way
MANY THANKS.
I will get back.

kanuns · October 4, 2022, 3:12pm

@david55
they have told me that they dont allow icmp so no PING response.

Anyhow, following is the trace/debug

it is from /var/log/asterisk/full

<------------->
[2022-10-04 20:08:42] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:42] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:42] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKlek4zudvbe0s3dlfqlzltzduu;Role=3;Hpt=8f78_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_18d_633c92c6_caeeab7_ex_8f78_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=t6yn4ynv-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as54eb9119
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:42] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:44] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKm1dwwo5wdh2w35mq8mwwj8mzd;Role=3;Hpt=8ea8_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_8a_633c92bc_ca3282f_ex_8ea8_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=sat96sy6-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:44] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:44] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:44] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKm1dwwo5wdh2w35mq8mwwj8mzd;Role=3;Hpt=8ea8_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_8a_633c92bc_ca3282f_ex_8ea8_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=sat96sy6-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as54e95bff
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:44] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:46] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKlek4zudvbe0s3dlfqlzltzduu;Role=3;Hpt=8f78_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_18d_633c92c6_caeeab7_ex_8f78_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=t6yn4ynv-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:46] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:46] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:46] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKlek4zudvbe0s3dlfqlzltzduu;Role=3;Hpt=8f78_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_18d_633c92c6_caeeab7_ex_8f78_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=t6yn4ynv-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as54eb9119
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:46] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKm1dwwo5wdh2w35mq8mwwj8mzd;Role=3;Hpt=8ea8_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_8a_633c92bc_ca3282f_ex_8ea8_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=sat96sy6-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKm1dwwo5wdh2w35mq8mwwj8mzd;Role=3;Hpt=8ea8_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_8a_633c92bc_ca3282f_ex_8ea8_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=sat96sy6-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as54e95bff
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c: Sending to 10.66.194.136:5060 (no NAT)
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as74d0e2d5
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:48] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:49] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:49] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:49] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:49] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as74d0e2d5
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:49] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:49] VERBOSE[2754] chan_sip.c: Really destroying SIP dialog '[email protected]' Method: OPTIONS
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKlek4zudvbe0s3dlfqlzltzduu;Role=3;Hpt=8f78_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_18d_633c92c6_caeeab7_ex_8f78_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=t6yn4ynv-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKlek4zudvbe0s3dlfqlzltzduu;Role=3;Hpt=8f78_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_18d_633c92c6_caeeab7_ex_8f78_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=t6yn4ynv-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as54eb9119
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as74d0e2d5
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:50] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as74d0e2d5
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKm1dwwo5wdh2w35mq8mwwj8mzd;Role=3;Hpt=8ea8_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_8a_633c92bc_ca3282f_ex_8ea8_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=sat96sy6-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKm1dwwo5wdh2w35mq8mwwj8mzd;Role=3;Hpt=8ea8_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_8a_633c92bc_ca3282f_ex_8ea8_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=sat96sy6-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as54e95bff
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:52] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:192.168.200.1:36738 --->


<------------->
[2022-10-04 20:08:54] VERBOSE[2754] chan_sip.c: Really destroying SIP dialog '863b047ddb4dfb11MjM4ZGZjMzJhNDIyZGY5MWRiZGNlMjA0OTA1MmViOTk.' Method: REGISTER
[2022-10-04 20:08:54] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKlek4zudvbe0s3dlfqlzltzduu;Role=3;Hpt=8f78_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_18d_633c92c6_caeeab7_ex_8f78_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=t6yn4ynv-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:54] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:54] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:54] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKlek4zudvbe0s3dlfqlzltzduu;Role=3;Hpt=8f78_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_18d_633c92c6_caeeab7_ex_8f78_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=t6yn4ynv-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as54eb9119
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:54] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bK3m99dcd3j9061a9gjf8543a8g;Role=3;Hpt=8ee8_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_c8_633c92d0_ca23b8d_ex_8ee8_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=istyfob9-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as74d0e2d5
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKm1dwwo5wdh2w35mq8mwwj8mzd;Role=3;Hpt=8ea8_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_8a_633c92bc_ca3282f_ex_8ea8_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=sat96sy6-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKm1dwwo5wdh2w35mq8mwwj8mzd;Role=3;Hpt=8ea8_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_8a_633c92bc_ca3282f_ex_8ea8_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=sat96sy6-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as54e95bff
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:56] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:58] VERBOSE[2754] chan_sip.c: Retransmitting #6 (no NAT) to 10.66.194.136:5060:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 10.66.200.158:5060;branch=z9hG4bK0f418276
Max-Forwards: 70
From: <sip:[email protected]>;tag=as6103b178
To: <sip:[email protected]>
Contact: <sip:[email protected]:5060>
Call-ID: [email protected]:5060
CSeq: 102 INVITE
User-Agent: IPBX-2.11.0.49(16.21.1)
Date: Tue, 04 Oct 2022 15:08:26 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 252

v=0
o=root 399385375 399385375 IN IP4 10.66.200.158
s=Asterisk PBX 16.21.1
c=IN IP4 10.66.200.158
t=0 0
m=audio 14698 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:150
a=sendrecv

---
[2022-10-04 20:08:58] VERBOSE[2754] chan_sip.c:
<--- SIP read from UDP:10.66.194.136:5060 --->
OPTIONS sip:10.66.200.158:5060 SIP/2.0
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKlek4zudvbe0s3dlfqlzltzduu;Role=3;Hpt=8f78_16;X-HwDim=4
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_18d_633c92c6_caeeab7_ex_8f78_16;CxtId=4;TRC=ffffffff-ffffffff>
Call-ID: [email protected]
From: <sip:10.66.194.136:5060>;tag=t6yn4ynv-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER,PUBLISH
Max-Forwards: 69
Content-Length: 0

<------------->
[2022-10-04 20:08:58] VERBOSE[2754] chan_sip.c: --- (10 headers 0 lines) ---
[2022-10-04 20:08:58] VERBOSE[2754] chan_sip.c: Looking for s in from-sip-external (domain 10.66.200.158)
[2022-10-04 20:08:58] VERBOSE[2754] chan_sip.c:
<--- Transmitting (no NAT) to 10.66.194.136:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.66.194.136:5060;branch=z9hG4bKlek4zudvbe0s3dlfqlzltzduu;Role=3;Hpt=8f78_16;X-HwDim=4;received=10.66.194.136
Record-Route: <sip:10.66.194.136:5060;transport=udp;lr;Hpt=nw_18d_633c92c6_caeeab7_ex_8f78_16;CxtId=4;TRC=ffffffff-ffffffff>
From: <sip:10.66.194.136:5060>;tag=t6yn4ynv-CC-1067-OFC-18
To: <sip:10.66.200.158:5060>;tag=as54eb9119
Call-ID: [email protected]
CSeq: 1 OPTIONS
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:10.66.200.158:5060>
Accept: application/sdp
Content-Length: 0


<------------>
[2022-10-04 20:08:58] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]' in 32000 ms (Method: OPTIONS)
[2022-10-04 20:08:58] WARNING[2754] chan_sip.c: Retransmission timeout reached on transmission [email protected]:5060 for seqno 102 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 31999ms with no response
[2022-10-04 20:08:58] WARNING[2754] chan_sip.c: Hanging up call [email protected]:5060 - no reply to our critical packet (see https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions).
[2022-10-04 20:08:58] VERBOSE[2754] chan_sip.c: Scheduling destruction of SIP dialog '[email protected]:5060' in 32000 ms (Method: INVITE)
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] app_dial.c: Everyone is busy/congested at this time (1:0/0/1)
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx.c: Executing [s@macro-dialout-trunk:26] NoOp("SIP/100-0000000a", "Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 18") in new stack
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx.c: Executing [s@macro-dialout-trunk:27] GotoIf("SIP/100-0000000a", "0?continue,1:s-CHANUNAVAIL,1") in new stack
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx_builtins.c: Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx.c: Executing [s-CHANUNAVAIL@macro-dialout-trunk:1] Set("SIP/100-0000000a", "RC=18") in new stack
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx.c: Executing [s-CHANUNAVAIL@macro-dialout-trunk:2] Goto("SIP/100-0000000a", "18,1") in new stack
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx_builtins.c: Goto (macro-dialout-trunk,18,1)
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx.c: Executing [18@macro-dialout-trunk:1] Goto("SIP/100-0000000a", "s-NOANSWER,1") in new stack
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx_builtins.c: Goto (macro-dialout-trunk,s-NOANSWER,1)
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx.c: Executing [s-NOANSWER@macro-dialout-trunk:1] NoOp("SIP/100-0000000a", "Dial failed due to trunk reporting NOANSWER - giving up") in new stack
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] pbx.c: Executing [s-NOANSWER@macro-dialout-trunk:2] Progress("SIP/100-0000000a", "") in new stack
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] chan_sip.c: Audio is at 10886
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] chan_sip.c: Adding codec gsm to SDP
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] chan_sip.c: Adding codec ulaw to SDP
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] chan_sip.c: Adding non-codec 0x1 (telephone-event) to SDP
[2022-10-04 20:08:58] VERBOSE[10072][C-00000006] chan_sip.c:
<--- Transmitting (no NAT) to 192.168.200.1:36738 --->
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 192.168.200.1:36738;branch=z9hG4bK-d87543-38559620ef11126f-1--d87543-;received=192.168.200.1;rport=36738
From: "100"<sip:[email protected]>;tag=364e9b5f
To: "03217169974"<sip:[email protected]>;tag=as5145e3b3
Call-ID: f06aea2e776f6e31MjM4ZGZjMzJhNDIyZGY5MWRiZGNlMjA0OTA1MmViOTk.
CSeq: 2 INVITE
Server: IPBX-2.11.0.49(16.21.1)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:[email protected]:5060>
Content-Type: application/sdp
Content-Length: 279

v=0
o=root 985569425 985569425 IN IP4 192.168.200.253
s=Asterisk PBX 16.21.1
c=IN IP4 192.168.200.253
t=0 0
m=audio 10886 RTP/AVP 3 0 101
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:150
a=sendrecv

<------------>

I know i am acting stupid, but please help

best regards,

david55 · October 4, 2022, 3:37pm

So why did they say:

There appears to be a good path from them to you, but they are completely ignoring things from you to them.

They are sending options very frequently assuming that they are actually seeing your reply, but one cannot rule out that they aren’t really just sending frequently. You should ask them if they see your OPTIONS. You should also try a call incoming through them (although if they are not seeing the reply to OPTIONS, they may consider you unreachable, and not deliver the call.

Also check that the router is actually forwarding to them.

kanuns · October 4, 2022, 6:05pm

@david55
I am not as learned as you. Can you please guide me a bit so that can argue with them.
What do you mean OPTIONS? This is the first time i am facing this kind of settings and issue. So im new to this.

This IP is directly connected to freepbx, no router from my side. just a fiber connection, via whch they provided me an IP and a gateway.,

Stewart1 · October 4, 2022, 6:24pm

Yes but you have two NICs and the routing at the OS level may not be correct.
From a root shell prompt type
ip route
and post the output.

david55 · October 4, 2022, 6:25pm

I thought, when you said they provided you with a gateway, that you meant they had provided you with a physical box.

Do you have a route defined to the fibre connection, for their server address. They’d still be able to send to you without a route, but anything you sent unsolicited would go the wrong way. This sounds to be an unusual arrangement. Are they also providing general internet access over the fibre, or is that a separate connection? With a separate connection, I think you will need a static route, defined at the OS level. This could be becoming a networking question, rather than a VoIP one.

OPTIONS, as used here, is a request that is used to test connectivity. If it gets a response, there is connectivity. It can provide other information, but it is unusual to use it in that way.

kanuns · October 4, 2022, 6:45pm

@Stewart1
default via 192.168.200.1 dev em1 proto dhcp metric 101
10.66.194.136 via 10.66.200.157 dev em4 proto static metric 100
10.66.200.156/30 dev em4 proto kernel scope link src 10.66.200.158 metric 100
10.74.193.8 via 10.66.200.157 dev em4 proto static metric 100
192.168.200.0/24 dev em1 proto kernel scope link src 192.168.200.253 metric 101

OR

That is something for me to Study now. I am a network guy, do this VoIP as a hobby but at the moment I am stuck.

No, no internet connection, just a SIP trunk.

kanuns · October 4, 2022, 6:47pm

@david55 when this is done please i need one more favor, please do recommend me a good book for this