Country Indication Tones wrong for 4 out of 5 numbers

Goochie · June 12, 2021, 1:50pm

I have a new install with 5 numbers. When you call my main number the dial tone is correct for New Zealand, but the other 4 is (I think) the US tone (1 long beep, 1 long pause). I have set the Country Indication Tone to New Zealand in Advanced Settings.

I thought the issue might be with my provider. I am using PJSip for extensions and the trunk to register 1 number. The other 4 are added to the main number as DDI’s and sent to extensions through Inbound Routes. The provider (KiwiVoIP) assures me the problem is not at their end.

I could really use your help on this, please.

Stewart1 · June 12, 2021, 2:38pm

With Inband Progress set for the trunk, and Indication Zone Country set as desired for the Inbound Route, a caller should hear that tone if the call is routed directly to an extension (unless Follow Me is enabled and Play Music On Hold is set to other than Ring).

I assume what you want to hear is
https://www.3amsystems.com/World_Tone_Database?q=New_Zealand,Ringing_tone
(click the yellow play icon).

If you still have trouble, paste the Asterisk log for a failing call at pastebin.freepx.org and post the link here (post last 8 hex characters if you are too new to post links).

Goochie · June 12, 2021, 2:48pm

Hey thank you Stewart for your response. Yes the dialtone in your link is what I am expecting to hear.

I will post the log as requested, but I have been doing some more testing and created a second trunk connection and put one of the DDI lines on that. I now get the correct dial tone.

So the issue seems clear that attaching DDI lines to piggyback into the PBX on1 trunk works fine except the dial tone ignores the Indication Zone Country setting for some reason. The SIP provider has just shrugged his shoulders and said “we don’t support FreePBX so you’re on your own if you want to use it”.

Stewart1 · June 12, 2021, 2:59pm

Possibly, the call is not being correctly associated with the trunk. In Asterisk SIP Settings, Allow Anonymous Inbound SIP Calls and Allow SIP Guests should normally be set to No. If you had to turn these on to receive calls to the problematic numbers, that is likely your issue.

A log including a SIP trace (at the Asterisk command prompt, type pjsip set logger on) should show whether this is a provider issue.

If all else fails, you could ‘answer’ the call before playing the ringing tone; the provider would have no control. However, this has some downsides, including that the caller would be charged for calls not actually answered by a human.

Goochie · June 12, 2021, 3:16pm

Unfortunately turning on those 2 SIP settings didn’t solve the problem. I turned on pjsip logger but I am not sure how to get this to you as I am a new poster here.

Charles_Darwin · June 12, 2021, 3:18pm

Insert the text, mark it, and press the </> button…if it works, you can see it on the right side…

answer

Goochie · June 12, 2021, 3:27pm

[2021-06-13 03:20:14] VERBOSE[16100] res_pjsip_logger.c: &lt;--- Transmitting SIP request (461 bytes) to UDP:27.111.14.67:5060 ---&gt;

3930OPTIONS sip:[email protected]:5060 SIP/2.0

3931Via: SIP/2.0/UDP 103.100.104.160:5060;rport;branch=z9hG4bKPj375b1212-0b4d-49cb-8729-4fe95cf63315

3932From: &lt;sip:[email protected]&gt;;tag=861746ad-ae2d-49eb-b238-f9935b67703b

3933To: &lt;sip:[email protected]&gt;

3934Contact: &lt;sip:[email protected]:5060&gt;

3935Call-ID: 15080bbc-72a2-4674-96c2-ded66d041175

3936CSeq: 41364 OPTIONS

3937Max-Forwards: 70

3938User-Agent: FPBX-15.0.17.34(18.3.0)

3939Content-Length: 0

3940

3941

3942[2021-06-13 03:20:14] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (552 bytes) from UDP:27.111.14.67:5060 ---&gt;

3943SIP/2.0 200 OK

3944Via: SIP/2.0/UDP 103.100.104.160:5060;branch=z9hG4bKPj375b1212-0b4d-49cb-8729-4fe95cf63315;received=103.100.104.160;rport=5060

3945From: &lt;sip:[email protected]&gt;;tag=861746ad-ae2d-49eb-b238-f9935b67703b

3946To: &lt;sip:[email protected]&gt;;tag=as0a5d68ad

3947Call-ID: 15080bbc-72a2-4674-96c2-ded66d041175

3948CSeq: 41364 OPTIONS

3949Server: NZ PBX

3950Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

3951Supported: replaces

3952Contact: &lt;sip:27.111.14.67:5060&gt;

3953Accept: application/sdp

3954Content-Length: 0

3955

3956

3957[2021-06-13 03:20:19] VERBOSE[16100] res_pjsip_logger.c: &lt;--- Transmitting SIP request (417 bytes) to UDP:192.168.1.21:5060 ---&gt;

3958OPTIONS sip:[email protected]:5060 SIP/2.0

3959Via: SIP/2.0/UDP 192.168.1.3:5060;rport;branch=z9hG4bKPj30f5d193-c71e-4a60-bb68-7d179388141b

3960From: &lt;sip:[email protected]&gt;;tag=0b3cc008-08fe-48b2-8a92-7f70bbcc3733

3961To: &lt;sip:[email protected]&gt;

3962Contact: &lt;sip:[email protected]:5060&gt;

3963Call-ID: 231d9d81-48c3-4cad-b709-2f52dbeee87c

3964CSeq: 33604 OPTIONS

3965Max-Forwards: 70

3966User-Agent: FPBX-15.0.17.34(18.3.0)

3967Content-Length: 0

3968

3969

3970[2021-06-13 03:20:19] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (357 bytes) from UDP:192.168.1.21:5060 ---&gt;

3971SIP/2.0 200 OK

3972Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPj30f5d193-c71e-4a60-bb68-7d179388141b

3973From: &lt;sip:[email protected]&gt;;tag=0b3cc008-08fe-48b2-8a92-7f70bbcc3733

3974To: &lt;sip:[email protected]&gt;;tag=839247466

3975Call-ID: 231d9d81-48c3-4cad-b709-2f52dbeee87c

3976CSeq: 33604 OPTIONS

3977User-Agent: Yealink SIP-T46S 66.86.0.15

3978Content-Length: 0

3979

3980

3981[2021-06-13 03:20:40] VERBOSE[24147] res_pjsip_logger.c: &lt;--- Transmitting SIP request (461 bytes) to UDP:27.111.14.67:5060 ---&gt;

3982OPTIONS sip:[email protected]:5060 SIP/2.0

3983Via: SIP/2.0/UDP 103.100.104.160:5060;rport;branch=z9hG4bKPjb559e33c-d117-42bd-9e4f-af62a4531625

3984From: &lt;sip:[email protected]&gt;;tag=f114f066-9b63-41f3-a9b8-7ee86b78b3e2

3985To: &lt;sip:[email protected]&gt;

3986Contact: &lt;sip:[email protected]:5060&gt;

3987Call-ID: 0e578062-ecf3-47c0-a550-2ff949bde4a1

3988CSeq: 13746 OPTIONS

3989Max-Forwards: 70

3990User-Agent: FPBX-15.0.17.34(18.3.0)

3991Content-Length: 0

3992

3993

3994[2021-06-13 03:20:40] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (552 bytes) from UDP:27.111.14.67:5060 ---&gt;

3995SIP/2.0 200 OK

3996Via: SIP/2.0/UDP 103.100.104.160:5060;branch=z9hG4bKPjb559e33c-d117-42bd-9e4f-af62a4531625;received=103.100.104.160;rport=5060

3997From: &lt;sip:[email protected]&gt;;tag=f114f066-9b63-41f3-a9b8-7ee86b78b3e2

3998To: &lt;sip:[email protected]&gt;;tag=as26eb8dda

3999Call-ID: 0e578062-ecf3-47c0-a550-2ff949bde4a1

4000CSeq: 13746 OPTIONS

4001Server: NZ PBX

4002Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

4003Supported: replaces

4004Contact: &lt;sip:27.111.14.67:5060&gt;

4005Accept: application/sdp

4006Content-Length: 0

4007

4008

4009[2021-06-13 03:20:49] VERBOSE[24147] res_pjsip_logger.c: &lt;--- Transmitting SIP request (417 bytes) to UDP:192.168.1.11:5060 ---&gt;

4010OPTIONS sip:[email protected]:5060 SIP/2.0

4011Via: SIP/2.0/UDP 192.168.1.3:5060;rport;branch=z9hG4bKPjc66ca0fa-13e8-4260-ae56-c8bdd509b8be

4012From: &lt;sip:[email protected]&gt;;tag=cfdece13-12c2-41d9-afc1-9f03002907ec

4013To: &lt;sip:[email protected]&gt;

4014Contact: &lt;sip:[email protected]:5060&gt;

4015Call-ID: 20c7f0e5-b455-4eba-83fb-661b6139646a

4016CSeq: 16404 OPTIONS

4017Max-Forwards: 70

4018User-Agent: FPBX-15.0.17.34(18.3.0)

4019Content-Length: 0

4020

4021

4022[2021-06-13 03:20:49] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (357 bytes) from UDP:192.168.1.11:5060 ---&gt;

4023SIP/2.0 200 OK

4024Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPjc66ca0fa-13e8-4260-ae56-c8bdd509b8be

4025From: &lt;sip:[email protected]&gt;;tag=cfdece13-12c2-41d9-afc1-9f03002907ec

4026To: &lt;sip:[email protected]&gt;;tag=935662855

4027Call-ID: 20c7f0e5-b455-4eba-83fb-661b6139646a

4028CSeq: 16404 OPTIONS

4029User-Agent: Yealink SIP-T46S 66.86.0.15

4030Content-Length: 0

4031

4032

4033[2021-06-13 03:21:09] VERBOSE[24147] res_pjsip_logger.c: &lt;--- Transmitting SIP request (417 bytes) to UDP:192.168.1.31:5060 ---&gt;

4034OPTIONS sip:[email protected]:5060 SIP/2.0

4035Via: SIP/2.0/UDP 192.168.1.3:5060;rport;branch=z9hG4bKPj8db8408f-4bf9-4304-a375-eb2320088d7a

4036From: &lt;sip:[email protected]&gt;;tag=35b12a2d-c421-4443-9201-6e38ecfc75ba

4037To: &lt;sip:[email protected]&gt;

4038Contact: &lt;sip:[email protected]:5060&gt;

4039Call-ID: ae296909-e9ec-480e-b662-7e860285a8fd

4040CSeq: 50826 OPTIONS

4041Max-Forwards: 70

4042User-Agent: FPBX-15.0.17.34(18.3.0)

4043Content-Length: 0

4044

4045

4046[2021-06-13 03:21:09] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (357 bytes) from UDP:192.168.1.31:5060 ---&gt;

4047SIP/2.0 200 OK

4048Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPj8db8408f-4bf9-4304-a375-eb2320088d7a

4049From: &lt;sip:[email protected]&gt;;tag=35b12a2d-c421-4443-9201-6e38ecfc75ba

4050To: &lt;sip:[email protected]&gt;;tag=706885992

4051Call-ID: ae296909-e9ec-480e-b662-7e860285a8fd

4052CSeq: 50826 OPTIONS

4053User-Agent: Yealink SIP-T46S 66.86.0.15

4054Content-Length: 0

4055

4056

4057[2021-06-13 03:21:14] VERBOSE[16100] res_pjsip_logger.c: &lt;--- Transmitting SIP request (461 bytes) to UDP:27.111.14.67:5060 ---&gt;

4058OPTIONS sip:[email protected]:5060 SIP/2.0

4059Via: SIP/2.0/UDP 103.100.104.160:5060;rport;branch=z9hG4bKPj31b3a7e7-63e6-43d4-bfd3-1085b905c10d

4060From: &lt;sip:[email protected]&gt;;tag=b531557b-97ff-43c5-97d4-8570b8c09bcf

4061To: &lt;sip:[email protected]&gt;

4062Contact: &lt;sip:[email protected]:5060&gt;

4063Call-ID: f3b81733-8b31-4d9d-a517-1078e7f1391d

4064CSeq: 52925 OPTIONS

4065Max-Forwards: 70

4066User-Agent: FPBX-15.0.17.34(18.3.0)

4067Content-Length: 0

4068

4069

4070[2021-06-13 03:21:14] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (552 bytes) from UDP:27.111.14.67:5060 ---&gt;

4071SIP/2.0 200 OK

4072Via: SIP/2.0/UDP 103.100.104.160:5060;branch=z9hG4bKPj31b3a7e7-63e6-43d4-bfd3-1085b905c10d;received=103.100.104.160;rport=5060

4073From: &lt;sip:[email protected]&gt;;tag=b531557b-97ff-43c5-97d4-8570b8c09bcf

4074To: &lt;sip:[email protected]&gt;;tag=as16044a26

4075Call-ID: f3b81733-8b31-4d9d-a517-1078e7f1391d

4076CSeq: 52925 OPTIONS

4077Server: NZ PBX

4078Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

4079Supported: replaces

4080Contact: &lt;sip:27.111.14.67:5060&gt;

4081Accept: application/sdp

4082Content-Length: 0

4083

4084

4085[2021-06-13 03:21:19] VERBOSE[16100] res_pjsip_logger.c: &lt;--- Transmitting SIP request (417 bytes) to UDP:192.168.1.21:5060 ---&gt;

4086OPTIONS sip:[email protected]:5060 SIP/2.0

4087Via: SIP/2.0/UDP 192.168.1.3:5060;rport;branch=z9hG4bKPj4aed2e9f-1524-4ea6-93dc-d203747849eb

4088From: &lt;sip:[email protected]&gt;;tag=380e8ea8-bee7-4951-b422-bda35a6c172a

4089To: &lt;sip:[email protected]&gt;

4090Contact: &lt;sip:[email protected]:5060&gt;

4091Call-ID: 3c4c5d65-c32f-4618-96c4-b9a56f85b32b

4092CSeq: 54767 OPTIONS

4093Max-Forwards: 70

4094User-Agent: FPBX-15.0.17.34(18.3.0)

4095Content-Length: 0

4096

4097

4098[2021-06-13 03:21:19] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (357 bytes) from UDP:192.168.1.21:5060 ---&gt;

4099SIP/2.0 200 OK

4100Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPj4aed2e9f-1524-4ea6-93dc-d203747849eb

4101From: &lt;sip:[email protected]&gt;;tag=380e8ea8-bee7-4951-b422-bda35a6c172a

4102To: &lt;sip:[email protected]&gt;;tag=839298237

4103Call-ID: 3c4c5d65-c32f-4618-96c4-b9a56f85b32b

4104CSeq: 54767 OPTIONS

4105User-Agent: Yealink SIP-T46S 66.86.0.15

4106Content-Length: 0

4107

4108

4109[2021-06-13 03:21:40] VERBOSE[24147] res_pjsip_logger.c: &lt;--- Transmitting SIP request (461 bytes) to UDP:27.111.14.67:5060 ---&gt;

4110OPTIONS sip:[email protected]:5060 SIP/2.0

4111Via: SIP/2.0/UDP 103.100.104.160:5060;rport;branch=z9hG4bKPja6f8841d-3b6c-4ea5-9d3c-000c76dd5d1b

4112From: &lt;sip:[email protected]&gt;;tag=0c825e7d-8a48-416c-87a0-1efe4fc5aa5b

4113To: &lt;sip:[email protected]&gt;

4114Contact: &lt;sip:[email protected]:5060&gt;

4115Call-ID: 36c42876-75d9-49ec-af23-0a041ddb1fc1

4116CSeq: 59965 OPTIONS

4117Max-Forwards: 70

4118User-Agent: FPBX-15.0.17.34(18.3.0)

4119Content-Length: 0

4120

4121

4122[2021-06-13 03:21:40] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (552 bytes) from UDP:27.111.14.67:5060 ---&gt;

4123SIP/2.0 200 OK

4124Via: SIP/2.0/UDP 103.100.104.160:5060;branch=z9hG4bKPja6f8841d-3b6c-4ea5-9d3c-000c76dd5d1b;received=103.100.104.160;rport=5060

4125From: &lt;sip:[email protected]&gt;;tag=0c825e7d-8a48-416c-87a0-1efe4fc5aa5b

4126To: &lt;sip:[email protected]&gt;;tag=as19f1e9f6

4127Call-ID: 36c42876-75d9-49ec-af23-0a041ddb1fc1

4128CSeq: 59965 OPTIONS

4129Server: NZ PBX

4130Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

4131Supported: replaces

4132Contact: &lt;sip:27.111.14.67:5060&gt;

4133Accept: application/sdp

4134Content-Length: 0

4135

4136

4137[2021-06-13 03:21:49] VERBOSE[24147] res_pjsip_logger.c: &lt;--- Transmitting SIP request (417 bytes) to UDP:192.168.1.11:5060 ---&gt;

4138OPTIONS sip:[email protected]:5060 SIP/2.0

4139Via: SIP/2.0/UDP 192.168.1.3:5060;rport;branch=z9hG4bKPjfbd14ba2-595a-49a9-a2b3-c7789859d910

4140From: &lt;sip:[email protected]&gt;;tag=ddf55aea-aef5-436d-b9ff-10b7fe72c779

4141To: &lt;sip:[email protected]&gt;

4142Contact: &lt;sip:[email protected]:5060&gt;

4143Call-ID: 867f6513-0a9c-4f26-9f85-1c1a70714ea0

4144CSeq: 62533 OPTIONS

4145Max-Forwards: 70

4146User-Agent: FPBX-15.0.17.34(18.3.0)

4147Content-Length: 0

4148

4149

4150[2021-06-13 03:21:49] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (357 bytes) from UDP:192.168.1.11:5060 ---&gt;

4151SIP/2.0 200 OK

4152Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPjfbd14ba2-595a-49a9-a2b3-c7789859d910

4153From: &lt;sip:[email protected]&gt;;tag=ddf55aea-aef5-436d-b9ff-10b7fe72c779

4154To: &lt;sip:[email protected]&gt;;tag=935766126

4155Call-ID: 867f6513-0a9c-4f26-9f85-1c1a70714ea0

4156CSeq: 62533 OPTIONS

4157User-Agent: Yealink SIP-T46S 66.86.0.15

4158Content-Length: 0

4159

4160

4161[2021-06-13 03:22:09] VERBOSE[24147] res_pjsip_logger.c: &lt;--- Transmitting SIP request (417 bytes) to UDP:192.168.1.31:5060 ---&gt;

4162OPTIONS sip:[email protected]:5060 SIP/2.0

4163Via: SIP/2.0/UDP 192.168.1.3:5060;rport;branch=z9hG4bKPj0d47100f-1d89-496c-add4-c8c14113136f

4164From: &lt;sip:[email protected]&gt;;tag=622fc773-f6cc-4dbe-81fd-50d1a92b6891

4165To: &lt;sip:[email protected]&gt;

4166Contact: &lt;sip:[email protected]:5060&gt;

4167Call-ID: 42ebcbb3-bf48-467a-abd3-bc2477de115c

4168CSeq: 34298 OPTIONS

4169Max-Forwards: 70

4170User-Agent: FPBX-15.0.17.34(18.3.0)

4171Content-Length: 0

4172

4173

4174[2021-06-13 03:22:09] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (357 bytes) from UDP:192.168.1.31:5060 ---&gt;

4175SIP/2.0 200 OK

4176Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPj0d47100f-1d89-496c-add4-c8c14113136f

4177From: &lt;sip:[email protected]&gt;;tag=622fc773-f6cc-4dbe-81fd-50d1a92b6891

4178To: &lt;sip:[email protected]&gt;;tag=706944873

4179Call-ID: 42ebcbb3-bf48-467a-abd3-bc2477de115c

4180CSeq: 34298 OPTIONS

4181User-Agent: Yealink SIP-T46S 66.86.0.15

4182Content-Length: 0

4183

4184

4185[2021-06-13 03:22:14] VERBOSE[16100] res_pjsip_logger.c: &lt;--- Transmitting SIP request (461 bytes) to UDP:27.111.14.67:5060 ---&gt;

4186OPTIONS sip:[email protected]:5060 SIP/2.0

4187Via: SIP/2.0/UDP 103.100.104.160:5060;rport;branch=z9hG4bKPj4f8a9869-acf3-40c9-a467-dfae35b99107

4188From: &lt;sip:[email protected]&gt;;tag=e9d9d855-f22b-427c-8146-a1abf67c1437

4189To: &lt;sip:[email protected]&gt;

4190Contact: &lt;sip:[email protected]:5060&gt;

4191Call-ID: 22e621e3-b0c2-4150-9356-fb70915b2b5b

4192CSeq: 38458 OPTIONS

4193Max-Forwards: 70

4194User-Agent: FPBX-15.0.17.34(18.3.0)

4195Content-Length: 0

4196

4197

4198[2021-06-13 03:22:14] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (552 bytes) from UDP:27.111.14.67:5060 ---&gt;

4199SIP/2.0 200 OK

4200Via: SIP/2.0/UDP 103.100.104.160:5060;branch=z9hG4bKPj4f8a9869-acf3-40c9-a467-dfae35b99107;received=103.100.104.160;rport=5060

4201From: &lt;sip:[email protected]&gt;;tag=e9d9d855-f22b-427c-8146-a1abf67c1437

4202To: &lt;sip:[email protected]&gt;;tag=as6f7c4604

4203Call-ID: 22e621e3-b0c2-4150-9356-fb70915b2b5b

4204CSeq: 38458 OPTIONS

4205Server: NZ PBX

4206Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE

4207Supported: replaces

4208Contact: &lt;sip:27.111.14.67:5060&gt;

4209Accept: application/sdp

4210Content-Length: 0

4211

4212

4213[2021-06-13 03:22:19] VERBOSE[16100] res_pjsip_logger.c: &lt;--- Transmitting SIP request (417 bytes) to UDP:192.168.1.21:5060 ---&gt;

4214OPTIONS sip:[email protected]:5060 SIP/2.0

4215Via: SIP/2.0/UDP 192.168.1.3:5060;rport;branch=z9hG4bKPj399358aa-8c35-44c6-a141-3c45f27bfb9f

4216From: &lt;sip:[email protected]&gt;;tag=a3f5b22a-127f-42f9-a73a-a03a3bd3293f

4217To: &lt;sip:[email protected]&gt;

4218Contact: &lt;sip:[email protected]:5060&gt;

4219Call-ID: 5ebea05e-0fdf-43e4-84e1-cbad9217f15e

4220CSeq: 30540 OPTIONS

4221Max-Forwards: 70

4222User-Agent: FPBX-15.0.17.34(18.3.0)

4223Content-Length: 0

4224

4225

4226[2021-06-13 03:22:19] VERBOSE[1574] res_pjsip_logger.c: &lt;--- Received SIP response (357 bytes) from UDP:192.168.1.21:5060 ---&gt;

4227SIP/2.0 200 OK

4228Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPj399358aa-8c35-44c6-a141-3c45f27bfb9f

4229From: &lt;sip:[email protected]&gt;;tag=a3f5b22a-127f-42f9-a73a-a03a3bd3293f

4230To: &lt;sip:[email protected]&gt;;tag=839336394

4231Call-ID: 5ebea05e-0fdf-43e4-84e1-cbad9217f15e

4232CSeq: 30540 OPTIONS

4233User-Agent: Yealink SIP-T46S 66.86.0.15

4234Content-Length: 0

Goochie · June 12, 2021, 3:27pm

Sorry guys, not sure how much of this you need

Stewart1 · June 12, 2021, 4:03pm

There is nothing useful in the log, even though it covers more than two minutes. Are you sure that the test call occurred during that interval?

15 seconds worth, starting with the incoming INVITE, should be sufficient. Or, paste a long log at pastebin.freepbx.org and post the link here (just the last 8 characters if you still are not allowed to post links).

Goochie · June 12, 2021, 4:22pm

Ok try this. I have definitely trapped the call here
https://pastebin.freepbx.org/view/abe2260a

Stewart1 · June 12, 2021, 4:36pm

Great, but pjsip logger was apparently not on. Note that restarting or reloading Asterisk (including Apply Config) will cancel it and you will have to issue pjsip set logger on again.

If that shows that the 183 progress was properly issued, we may need a packet capture to see whether the correct ring tone sound was transmitted.

Goochie · June 12, 2021, 4:55pm

Ok tried again
https://pastebin.freepbx.org/view/b17bdbb6

Stewart1 · June 12, 2021, 5:10pm

OK, good log. Line 484:

[2021-06-13 04:47:42] VERBOSE[16100] res_pjsip_logger.c: &lt;--- Transmitting SIP response (534 bytes) to UDP:27.111.14.67:5060 ---&gt;      
SIP/2.0 180 Ringing

The 180 leaves it up to the provider (or in some cases the caller’s carrier or device) what ring tone to play.

Now, to determine whether this is a configuration error or a bug. Confirm that for the trunk KiwiVoIP, Inband Progress is set to Yes. If so, I’ll try to duplicate the trouble here.

Goochie · June 12, 2021, 5:17pm

It was set to No.

Stewart1 · June 12, 2021, 5:40pm

If setting it to Yes doesn’t help, paste a new log.

Goochie · June 12, 2021, 5:40pm

I set the Inband Progress to Yes, did a reboot for good measure and tried again. This was the result.

Goochie · June 12, 2021, 5:41pm

16030	[2021-06-13 05:31:29] VERBOSE[5633][C-00000003] app_dial.c: Connected line update to PJSIP/KiwiVoIP-00000004 prevented.	
16031	[2021-06-13 05:31:29] VERBOSE[2549] res_pjsip_logger.c: <--- Received SIP response (367 bytes) from UDP:192.168.1.31:5060 --->	
16032	SIP/2.0 100 Trying	
16033	Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPj6c200416-ce3a-4fc2-9987-cbfa0f3a1e43	
16034	From: "Graham Young" <sip:[email protected]>;tag=a49b099d-d946-4f0d-9476-0b5e1267fa65	
16035	To: <sip:[email protected]>	
16036	Call-ID: d2d16eba-dac1-4bfd-8d74-27bcd425101b	
16037	CSeq: 23786 INVITE	
16038	User-Agent: Yealink SIP-T46S 66.86.0.15	
16039	Content-Length: 0	
16040		
16041		
16042	[2021-06-13 05:31:29] VERBOSE[2549] res_pjsip_logger.c: <--- Received SIP response (590 bytes) from UDP:192.168.1.31:5060 --->	
16043	SIP/2.0 180 Ringing	
16044	Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPj6c200416-ce3a-4fc2-9987-cbfa0f3a1e43	
16045	From: "Graham Young" <sip:[email protected]>;tag=a49b099d-d946-4f0d-9476-0b5e1267fa65	
16046	To: <sip:[email protected]>;tag=716440113	
16047	Call-ID: d2d16eba-dac1-4bfd-8d74-27bcd425101b	
16048	CSeq: 23786 INVITE	
16049	Contact: <sip:[email protected]:5060>	
16050	Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE	
16051	User-Agent: Yealink SIP-T46S 66.86.0.15	
16052	Allow-Events: talk,hold,conference,refer,check-sync	
16053	Content-Length: 0	
16054		
16055		
16056	[2021-06-13 05:31:29] VERBOSE[5633][C-00000003] app_dial.c: PJSIP/802-00000005 is ringing	
16057	[2021-06-13 05:31:29] VERBOSE[2550] res_pjsip_logger.c: <--- Transmitting SIP response (867 bytes) to UDP:27.111.14.67:5060 --->	
16058	SIP/2.0 183 Session Progress	
16059	Via: SIP/2.0/UDP 27.111.14.67:5060;rport=5060;received=27.111.14.67;branch=z9hG4bK7bb7d668	
16060	Call-ID: [email protected]	
16061	From: "Graham Young" <sip:[email protected]>;tag=as3f02ae27	
16062	To: <sip:[email protected]>;tag=968d5316-3336-4c3d-b298-45de5e5b23ab	
16063	CSeq: 102 INVITE	
16064	Server: FPBX-15.0.17.34(18.3.0)	
16065	Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, MESSAGE, REFER	
16066	Contact: <sip:103.100.104.160:5060>	
16067	Content-Type: application/sdp	
16068	Content-Length: 290	
16069		
16070	v=0	
16071	o=- 1732719017 1732719019 IN IP4 103.100.104.160	
16072	s=Asterisk	
16073	c=IN IP4 103.100.104.160	
16074	t=0 0	
16075	m=audio 19844 RTP/AVP 3 8 0 101	
16076	a=rtpmap:3 GSM/8000	
16077	a=rtpmap:8 PCMA/8000	
16078	a=rtpmap:0 PCMU/8000	
16079	a=rtpmap:101 telephone-event/8000	
16080	a=fmtp:101 0-16	
16081	a=ptime:20	
16082	a=maxptime:150	
16083	a=sendrecv	
16084		
16085	[2021-06-13 05:31:39] VERBOSE[2550] res_pjsip_logger.c: <--- Transmitting SIP request (461 bytes) to UDP:27.111.14.67:5060 --->	
16086	OPTIONS sip:[email protected]:5060 SIP/2.0	
16087	Via: SIP/2.0/UDP 103.100.104.160:5060;rport;branch=z9hG4bKPj7365d14f-bba9-46a0-913c-7d835ff54ee4	
16088	From: <sip:[email protected]>;tag=4c188da3-d387-429c-8e0d-2dcadb66c940	
16089	To: <sip:[email protected]>	
16090	Contact: <sip:[email protected]:5060>	
16091	Call-ID: 1b531856-4416-4215-aefd-1efad833d745	
16092	CSeq: 35068 OPTIONS	
16093	Max-Forwards: 70	
16094	User-Agent: FPBX-15.0.17.34(18.3.0)	
16095	Content-Length: 0	
16096		
16097		
16098	[2021-06-13 05:31:39] VERBOSE[2549] res_pjsip_logger.c: <--- Received SIP response (552 bytes) from UDP:27.111.14.67:5060 --->	
16099	SIP/2.0 200 OK	
16100	Via: SIP/2.0/UDP 103.100.104.160:5060;branch=z9hG4bKPj7365d14f-bba9-46a0-913c-7d835ff54ee4;received=103.100.104.160;rport=5060	
16101	From: <sip:[email protected]>;tag=4c188da3-d387-429c-8e0d-2dcadb66c940	
16102	To: <sip:[email protected]>;tag=as1015caf7	
16103	Call-ID: 1b531856-4416-4215-aefd-1efad833d745	
16104	CSeq: 35068 OPTIONS	
16105	Server: NZ PBX	
16106	Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE	
16107	Supported: replaces	
16108	Contact: <sip:27.111.14.67:5060>	
16109	Accept: application/sdp	
16110	Content-Length: 0	
16111		
16112		
16113	[2021-06-13 05:31:43] VERBOSE[2550] res_pjsip_logger.c: <--- Transmitting SIP request (417 bytes) to UDP:192.168.1.21:5060 --->	
16114	OPTIONS sip:[email protected]:5060 SIP/2.0	
16115	Via: SIP/2.0/UDP 192.168.1.3:5060;rport;branch=z9hG4bKPj6c82ef71-059f-48ad-bdb9-2bcff2625f54	
16116	From: <sip:[email protected]>;tag=baaf8be3-8d12-4617-88f9-5945e482ddd8	
16117	To: <sip:[email protected]>	
16118	Contact: <sip:[email protected]:5060>	
16119	Call-ID: f21f3ab7-9a40-4a54-945e-8842e1e3956d	
16120	CSeq: 46412 OPTIONS	
16121	Max-Forwards: 70	
16122	User-Agent: FPBX-15.0.17.34(18.3.0)	
16123	Content-Length: 0	
16124		
16125		
16126	[2021-06-13 05:31:43] VERBOSE[2549] res_pjsip_logger.c: <--- Received SIP response (357 bytes) from UDP:192.168.1.21:5060 --->	
16127	SIP/2.0 200 OK	
16128	Via: SIP/2.0/UDP 192.168.1.3:5060;rport=5060;branch=z9hG4bKPj6c82ef71-059f-48ad-bdb9-2bcff2625f54	
16129	From: <sip:[email protected]>;tag=baaf8be3-8d12-4617-88f9-5945e482ddd8	
16130	To: <sip:[email protected]>;tag=848504091	
16131	Call-ID: f21f3ab7-9a40-4a54-945e-8842e1e3956d	
16132	CSeq: 46412 OPTIONS	
16133	User-Agent: Yealink SIP-T46S 66.86.0.15	
16134	Content-Length: 0	
16135		
16136		
16137	[2021-06-13 05:31:43] VERBOSE[2549] res_pjsip_logger.c: <--- Received SIP request (357 bytes) from UDP:27.111.14.67:5060 --->	
16138	CANCEL sip:[email protected]:5060 SIP/2.0	
16139	Via: SIP/2.0/UDP 27.111.14.67:5060;branch=z9hG4bK7bb7d668;rport	
16140	Max-Forwards: 70	
16141	From: "Graham Young" <sip:[email protected]>;tag=as3f02ae27	
16142	To: <sip:[email protected]:5060>	
16143	Call-ID: [email protected]	
16144	CSeq: 102 CANCEL	
16145	User-Agent: NZ PBX	
16146	Content-Length: 0	
16147

Stewart1 · June 12, 2021, 6:06pm

So now we did send a 183 Session Progress. Possibly the provider didn’t honor it, or it could have incorrect cadence. Conceivably, a codec issue; the first preference codec offered is GSM, which the provider likely doesn’t support. It should ignore that, but sometimes things go awry. To be certain, remove GSM from the trunk codec list (leave only alaw and ulaw) and try again.

If that doesn’t help, capture traffic with tcpdump and listen to the audio with Wireshark to confirm that the sound played is the NZ ring tone. If it is, this seems like a provider problem; you could try a different one to confirm. If not, we need to track down why the Country Indication was not followed.

david55 · June 12, 2021, 6:08pm

If this call is arriving from an iTSP, I wouldn’t expect them to honour early media, as that would allow you to provide free services. The only way of generating an appropriate ring back tone, in that case would be to answer the call, but that is not a friendly thing to do as it starts billing for the caller.

More likely if it isn’t an ITSP is that, if the caller uses late offer SDP, as Cisco systems do in many cases, there be no way of knowing where to send the early media. You haven’t included the incoming INVITE, so it is not possible to tell whether this is the case.

Stewart1 · June 12, 2021, 6:11pm

True, but the incoming INVITE was pasted in an earlier post and it did offer alaw SDP. IMO it’s very unlikely to have changed.