ALERT GVSIP Is Dead, was: GVSIP Registration Issues. Asterisk 13.23.0 Seems To Fix The Problem.

[Vladimir Mikhelson]

Hi,

I have noticed all GVSIP calls started failing some time today, August 14, 2018. Incoming calls also did not go through.

Verified all registrations, see below:

<Registration/ServerURI..............................> <Auth..........> <Status.......>

==========================================================================================


gvsip1/sipbihai.sip.google.com gvsip1 Registered

gvsip2/sipbihai.sip.google.com gvsip2 Registered

gvsip3/sipbihai.sip.google.com gvsip3 Registered

gvsip4/sipbihai.sip.google.com gvsip4 Registered

gvsip5/sipbihai.sip.google.com gvsip5 Registered

gvsip6/sipbihai.sip.google.com gvsip6 Registered

gvsip7/sipbihai.sip.google.com gvsip7 Registered

gvsip8/sipbihai.sip.google.com gvsip8 Registered

gvsip9/sipbihai.sip.google.com gvsip9 Registered


Objects found: 9


Restarted via "amportal restart", observed all registrations failed, see below:

<Registration/ServerURI..............................> <Auth..........> <Status.......>

==========================================================================================


gvsip1/sipbihai.sip.google.com gvsip1 Unregistered

gvsip2/sipbihai.sip.google.com gvsip2 Unregistered

gvsip3/sipbihai.sip.google.com gvsip3 Unregistered

gvsip4/sipbihai.sip.google.com gvsip4 Unregistered

gvsip5/sipbihai.sip.google.com gvsip5 Unregistered

gvsip6/sipbihai.sip.google.com gvsip6 Unregistered

gvsip7/sipbihai.sip.google.com gvsip7 Unregistered

gvsip8/sipbihai.sip.google.com gvsip8 Unregistered

gvsip9/sipbihai.sip.google.com gvsip9 Unregistered


Objects found: 9

Any ideas anybody?

Thank you,
Vladimir

 

[Vladimir Mikhelson]

Additional information.

Here is a sample call log:

-- Called PJSIP/1NXXNXXXX@gvsip1

[2018-08-14 20:35:28] DEBUG[2876]: res_pjsip_outbound_registration.c:2577 handle_outgoing_request: Found matching outbound registration state

<--- Transmitting SIP request (1608 bytes) to TLS:64.9.242.108:5061 --->

INVITE sip:[email protected] SIP/2.0

Via: SIP/2.0/TLS 10.10.10.10:5061;rport;branch=z9hG4bKPjd78f635f-b76c-4e77-91e6-9e1033aa3d17;alias

From: "The CID Name" <sip:[email protected]>;tag=9d72b084-0c7e-46bf-8c85-147f77ff3eb8

To: <sip:[email protected]>

Contact: <sip:[email protected]:5061;transport=TLS>

Call-ID: 912f9e7e-99e9-44f5-83a6-eda61b11db13

CSeq: 22042 INVITE

Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, REFER, MESSAGE

Supported: 100rel, timer, replaces, norefersub, path, outbound

Session-Expires: 1800

Min-SE: 90

P-Preferred-Identity:

Max-Forwards: 70

User-Agent: Asterisk PBX 13.22.0

Content-Type: application/sdp

Content-Length: 844


v=0

o=- 1002156393 1002156393 IN IP4 10.10.10.10

s=Asterisk

c=IN IP4 10.10.10.10

t=0 0

m=audio 16676 RTP/AVP 0 101

a=ice-ufrag:4cdbd46d23bd98981ca04de26d57cb88

a=ice-pwd:6741290a7e83f12e2802ee3c1b16b174

a=candidate:H3f1aa6b9 1 UDP 2130706431 fe80::f850:a878:8eb0:4c49 16676 typ host

a=candidate:Hac11892c 1 UDP 2130706431 10.10.10.10 16676 typ host

a=candidate:S6b8f7e01 1 UDP 1694498815 <public-IP> 7399 typ srflx raddr 10.10.10.10 rport 16676

a=candidate:H3f1aa6b9 2 UDP 2130706430 fe80::f850:a878:8eb0:4c49 16677 typ host

a=candidate:Hac11892c 2 UDP 2130706430 10.10.10.10 16677 typ host

a=candidate:S6b8f7e01 2 UDP 1694498814 <public-IP> 24915 typ srflx raddr 10.10.10.10 rport 16677

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=maxptime:150

a=sendrecv

a=rtcp-mux


[2018-08-14 20:35:38] WARNING[30989]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000

 

[tycho]

Not having that problem on my PBX:

Chan_PJSip Registrations
           

 <Registration/ServerURI..............................>  <Auth..........>  <Status.......>
==========================================================================================

 gvsip1/sip:obihai.sip.google.com                        gvsip1            Registered

 

[Vladimir Mikhelson]

Interestingly, PJSIP debug shows, "<--- Transmitting SIP request (1608 bytes) to TLS:64.9.242.108:5061 --->"
whereas pjsip_custom.conf lists outbound_proxy=sipbihai.telephony.goog:5061..." and obihai.telephony.goog translates into
64.9.243.172 or 64.9.243.108 but never into 64.9.242.108

Can somebody shed some light on this discrepancy?

 

[Vladimir Mikhelson]

The problem is supposedly solved, but I am not sure what was the root cause.

I started playing with the URI in the outbound_proxy statement in the gvsip1 / type=registration section of the josip_custom.conf. Specifically, I replaced obihai.telephony.goog with 64.9.243.108, ran "core reload" and observed gvsip1 registered and other 8 trunks unregistered. Test call still produced transmitting to 64.9.242.108 as apparently it used gvsip1 / type=endpoint section where I did not make any changes. All responses were coming from 64.9.243.108 though. Then I reverted gvsip1 to the original URI, performed "core reload," and observed gvsip1 still registered and all other trunks unregistered.

Then I made the same modification to gvsip9. Observed the same result.

Then I reverted all outbound_proxy statements I played with to the original URI value of obihai.telephony.goog, ran "amportal restart" and observed all trunks registered.

So it was either some strange bug / feature in the Asterisk 13 pjsip name resolution implementation or Google changed A records and failed to change SRV records or something else of that nature.

As of this moment the name resolution is as follows:

> set type=srv
> _sip._tls.obihai.telephony.goog.
Server: unx.int.hci2.com
Address: 172.17.135.3

Non-authoritative answer:
_sip._tls.obihai.telephony.goog SRV service location:
priority = 20
weight = 0
port = 5061
svr hostname = gm-voice.l.google.com

telephony.goog nameserver = ns3.google.com
telephony.goog nameserver = ns1.google.com
telephony.goog nameserver = ns4.google.com
telephony.goog nameserver = ns2.google.com
ns1.google.com internet address = 216.239.32.10
ns1.google.com AAAA IPv6 address = 2001:4860:4802:32::a
ns2.google.com internet address = 216.239.34.10
ns2.google.com AAAA IPv6 address = 2001:4860:4802:34::a
ns3.google.com internet address = 216.239.36.10
ns3.google.com AAAA IPv6 address = 2001:4860:4802:36::a
ns4.google.com internet address = 216.239.38.10
ns4.google.com AAAA IPv6 address = 2001:4860:4802:38::a
> set type=a
> gm-voice.l.google.com.
Server: unx.int.hci2.com
Address: 172.17.135.3

Non-authoritative answer:
Name: gm-voice.l.google.com
Address: 64.9.243.108

> obihai.telephony.goog.
Server: unx.int.hci2.com
Address: 172.17.135.3

Non-authoritative answer:
Name: obihai.telephony.goog
Address: 64.9.243.108

As we can see gm-voice.l.google.com and obihai.telephony.goog resolve consistently. It could have been different at the time of the problem occurrence.

 

[Vladimir Mikhelson]

Saga continues.

In the morning calls did not go through again even though the Asterisk showed all PJSIP trunks registered. "Amportal restart" apparently fixed the issue.

Interestingly, all SIP conversations during incoming and outgoing calls go to or come from TLS:64.9.242.108:5061 whereas all registrations are handled by
TLS:64.9.243.108:5061. Both obihai.telephony.goog and gm-voice.l.google.com resolve to 64.9.243.108. It still escapes me where this 64.9.242.108 IP is coming from.

Once in a while I see the following series of messages on the Asterisk console:

[2018-08-15 11:23:18] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-15 11:23:18] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-15 11:23:18] ERROR[28101]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message
[2018-08-15 11:23:18] ERROR[31963]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message
[2018-08-15 11:27:32] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000

After the last one off these series Asterisk has started sending registrations to 64.9.242.108 as well.

It looks like Google may be changing something on their end. Another theory is that my edge firewall may not pass incoming traffic from an unknown IP on port 5061.

 

[Vladimir Mikhelson]

Everything is stable for the last 2 weeks. My conclusion Google was probably changing something on their end on August 14, 2018.

I am seeing SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000 periodically. IP switching follows, but no service interruptions are observed..

 

[Vladimir Mikhelson]

Yesterday comment was too early.

Observed a weird case of a single registration not working. Specifically, Asterisk reported "Registered" whereas incoming Google Voice calls did not go through. "pjsip send register gvsipx" produced the "res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message" The only search result using Google search engine was my own thread. Changing the title to "No Joy" to reflect the real state of the investigation.

 

[Vladimir Mikhelson]

It turned out all registrations are showing "Registered" in "pjsip show registrations" but calls fail both ways.

"pjsip send register gvsipx" fixes the problem for a short period of time, then the next series of SSL Error messages show up like these:

[2018-08-29 10:47:55] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-29 10:47:56] ERROR[28101]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message
[2018-08-29 10:47:59] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-29 10:47:59] ERROR[30033]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message
[2018-08-29 10:48:08] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-29 10:48:08] ERROR[30033]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message
[2018-08-29 10:48:19] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-29 10:48:19] ERROR[30033]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message
[2018-08-29 10:48:22] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-29 10:48:22] ERROR[30033]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message
[2018-08-29 10:48:28] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-29 10:48:28] ERROR[30033]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message
[2018-08-29 10:48:30] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-29 10:48:30] ERROR[30033]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message
[2018-08-29 10:48:38] WARNING[28101]: pjproject:0 <?>: SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-08-29 10:48:38] ERROR[30033]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message

and the only remedy which still seems to work is "amportal restart"

 

[Vladimir Mikhelson]

Night of 09/10/2018. Updated to Asterisk 13.23.0 which seems to have fixed the issue. At least I do not see the SSL 6 [SSL_ERROR_ZERO_RETURN] errors any more and registrations seem to actually stay uninterrupted.

 

[mardosas]

Hi,

How did you the upgrade to Asterisk 13.23.0?

 

[jerrm]

We just uncovered similar issues as this on a lightly used GV number. Two GV trunks on the box, one has been flawless. The other seems to stop working every other day or so. The trunk says registered, but stops working. Pjsip send register didn't do any good. Only a restart brings it back. The unit restarts asterisk nightly for backup, and that was probably masking the symptoms.

A quick glance at the logs had me thinking it might be something with the oauth access key refresh, but I haven't really dug into it.

 

[Vladimir Mikhelson]

Hi,

How did you the upgrade to Asterisk 13.23.0?

cd /usr/src
wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-13-current.tar.gz
tar xvfz asterisk-13-current.tar.gz
cd asterisk-13.23.0/
contrib/scripts/get_mp3_source.sh
contrib/scripts/install_prereq install
patch -p1 < ../gvsip-naf.patch
./configure --with-pjproject-bundled --with-jansson-bundled
make menuselect
make
ldconfig
make install
amportal restart

Notes:

• gvsip-naf.patch was present in /usr/src

 

[mardosas]

Hi Vladimir,

I see. Many thanks for the info!

 

[Vladimir Mikhelson]

We just uncovered similar issues as this on a lightly used GV number. Two GV trunks on the box, one has been flawless. The other seems to stop working every other day or so. The trunk says registered, but stops working. Pjsip send register didn't do any good. Only a restart brings it back. The unit restarts asterisk nightly for backup, and that was probably masking the symptoms.

A quick glance at the logs had me thinking it might be something with the oauth access key refresh, but I haven't really dug into it.

I am not a pjsip guru yet, cannot comment on it with complete understanding.

What I was seeing in 13.22 were log sequences similar to the below:

[2018-08-27 23:51:46] ERROR[28101] res_pjsip_outbound_registration.c: Resolver failed. Cannot send message
[2018-08-27 23:51:54] ERROR[17308] res_pjsip_outbound_registration.c: Resolver failed. Cannot send message
[2018-08-27 23:52:07] DEBUG[17308] res_pjsip_outbound_registration.c: Registration re-using transport 0x6c29b9ac
[2018-08-27 23:52:07] WARNING[17308] res_pjsip_outbound_registration.c: No response received from 'sip:obihai.sip.google.com' on registration attempt to 'sip:[email protected]', retrying in '60'
[2018-08-27 23:53:07] DEBUG[17308] res_pjsip_outbound_registration.c: Registration re-using transport 0x6c29b9ac

or

[2018-09-02 21:23:48] NOTICE[1767] res_stun_monitor.c: Old external address/port 0.0.0.0:0 now seen as 10.10.10.10:31250.
[2018-09-02 21:23:53] WARNING[1759] res_pjsip_outbound_registration.c: No response received from 'sip:obihai.sip.google.com' on registration attempt to 'sip:[email protected]', retrying in '60'
[2018-09-02 21:23:53] WARNING[1759] res_pjsip_outbound_registration.c: No response received from 'sip:obihai.sip.google.com' on registration attempt to 'sip:[email protected]', retrying in '60'
[2018-09-02 21:24:53] DEBUG[1759] res_pjsip_outbound_registration.c: Registration re-using transport 0x76102a8c
[2018-09-02 21:24:53] DEBUG[2364] res_pjsip_outbound_registration.c: Registration re-using transport 0x7611513c
[2018-09-02 21:24:53] DEBUG[1759] res_pjsip_outbound_registration.c: Stored service-route: <sip:ADW...74A;lr>Service-Route
[2018-09-02 21:24:53] DEBUG[1759] res_pjsip_outbound_registration.c: Stored service-route: <sip:ADA...WGD:5060;transport=udp;lr;uri-econt=H44BFVE3D>
[2018-09-02 21:24:53] DEBUG[1759] res_pjsip_outbound_registration.c: Stored associated uri: <sip:[email protected]>P-Associated-URI<E0>^U<8A>m<80>^L<8A>m
[2018-09-02 21:24:54] DEBUG[1759] res_pjsip_outbound_registration.c: Stored service-route: <sip:ADW2...SRWWY4LBCFXG;lr>r>Service-Route
[2018-09-02 21:24:54] DEBUG[1759] res_pjsip_outbound_registration.c: Stored service-route: <sip:ADA...U6RD:5060;transport=udp;lr;uri-econt=N3ZD74WKJ>
[2018-09-02 21:24:54] DEBUG[1759] res_pjsip_outbound_registration.c: Stored associated uri: <sip:[email protected]>P-Associated-URI<E0>^U<8A>m<80>^L<8A>m
[2018-09-02 21:33:25] WARNING[1758] pjproject:             SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-09-02 21:33:26] DEBUG[1758] res_pjsip_outbound_registration.c: Registration using newly created transport 0x7610ba7c
[2018-09-02 21:33:26] WARNING[1758] pjproject:             SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-09-02 21:33:26] DEBUG[3240] res_pjsip_outbound_registration.c: Registration using newly created transport 0x75b18ef4

And no matter what in 13.22 all GVSIP trunks always showed "Registered"

After the 13.23 upgrade one of the GVSIP trunks showed "Rejected" so I issued "pjsip send register gvsipX"

The log showed:

[2018-09-10 22:31:29] NOTICE[15960] res_stun_monitor.c: Old external address/port 0.0.0.0:0 now seen as 10.10.10.10.1:17522.
[2018-09-10 22:31:34] WARNING[15948] res_pjsip_outbound_registration.c: No response received from 'sip:obihai.sip.google.com' on registration attempt to 'sip:[email protected]', retrying in '60'
[2018-09-10 22:32:19] DEBUG[15948] res_pjsip_outbound_registration.c: Registration re-using transport 0x76042cac
[2018-09-10 22:32:20] WARNING[15947] pjproject:                    SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-09-10 22:32:25] DEBUG[15948] res_pjsip_outbound_registration.c: Registration using newly created transport 0x7604aeb4
[2018-09-10 22:32:25] DEBUG[15948] res_pjsip_outbound_registration.c: Stored service-route: <sip:ACAH...VH:5060;uri-econt=5FSPR673RW..MYI

And all I see ever after are the happy sequences like this:

[2018-09-10 23:29:45] DEBUG[20891] res_pjsip_outbound_registration.c: Stored service-route: <sip:ABZ...BVYIV:5060;transport=udp;lr;uri-econt=ZUGQBPSTW>
[2018-09-10 23:29:45] DEBUG[20891] res_pjsip_outbound_registration.c: Stored associated uri: <sip:[email protected]>P-Associated-URI<90>RQ^B0IQ^B
[2018-09-10 23:30:41] DEBUG[20891] res_pjsip_outbound_registration.c: Registration re-using transport 0x24eb28c
[2018-09-10 23:30:41] DEBUG[20891] res_pjsip_outbound_registration.c: Stored service-route: <sip:ACAH...W25:5060;uri-econt=5O6...4FTA;lr>Service-Route

 

[jerrm]

I am not a pjsip guru yet, cannot comment on it with complete understanding.

What I was seeing in 13.22 were log sequences similar to the below:

[2018-08-27 23:51:46] ERROR[28101] res_pjsip_outbound_registration.c: Resolver failed. Cannot send message
[2018-08-27 23:51:54] ERROR[17308] res_pjsip_outbound_registration.c: Resolver failed. Cannot send message
[2018-08-27 23:52:07] DEBUG[17308] res_pjsip_outbound_registration.c: Registration re-using transport 0x6c29b9ac
[2018-08-27 23:52:07] WARNING[17308] res_pjsip_outbound_registration.c: No response received from 'sip:obihai.sip.google.com' on registration attempt to 'sip:[email protected]', retrying in '60'
[2018-08-27 23:53:07] DEBUG[17308] res_pjsip_outbound_registration.c: Registration re-using transport 0x6c29b9ac

or

[2018-09-02 21:23:48] NOTICE[1767] res_stun_monitor.c: Old external address/port 0.0.0.0:0 now seen as 10.10.10.10:31250.
[2018-09-02 21:23:53] WARNING[1759] res_pjsip_outbound_registration.c: No response received from 'sip:obihai.sip.google.com' on registration attempt to 'sip:[email protected]', retrying in '60'
[2018-09-02 21:23:53] WARNING[1759] res_pjsip_outbound_registration.c: No response received from 'sip:obihai.sip.google.com' on registration attempt to 'sip:[email protected]', retrying in '60'
[2018-09-02 21:24:53] DEBUG[1759] res_pjsip_outbound_registration.c: Registration re-using transport 0x76102a8c
[2018-09-02 21:24:53] DEBUG[2364] res_pjsip_outbound_registration.c: Registration re-using transport 0x7611513c
[2018-09-02 21:24:53] DEBUG[1759] res_pjsip_outbound_registration.c: Stored service-route: <sip:ADW...74A;lr>Service-Route
[2018-09-02 21:24:53] DEBUG[1759] res_pjsip_outbound_registration.c: Stored service-route: <sip:ADA...WGD:5060;transport=udp;lr;uri-econt=H44BFVE3D>
[2018-09-02 21:24:53] DEBUG[1759] res_pjsip_outbound_registration.c: Stored associated uri: <sip:[email protected]>P-Associated-URI<E0>^U<8A>m<80>^L<8A>m
[2018-09-02 21:24:54] DEBUG[1759] res_pjsip_outbound_registration.c: Stored service-route: <sip:ADW2...SRWWY4LBCFXG;lr>r>Service-Route
[2018-09-02 21:24:54] DEBUG[1759] res_pjsip_outbound_registration.c: Stored service-route: <sip:ADA...U6RD:5060;transport=udp;lr;uri-econt=N3ZD74WKJ>
[2018-09-02 21:24:54] DEBUG[1759] res_pjsip_outbound_registration.c: Stored associated uri: <sip:[email protected]>P-Associated-URI<E0>^U<8A>m<80>^L<8A>m
[2018-09-02 21:33:25] WARNING[1758] pjproject:             SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-09-02 21:33:26] DEBUG[1758] res_pjsip_outbound_registration.c: Registration using newly created transport 0x7610ba7c
[2018-09-02 21:33:26] WARNING[1758] pjproject:             SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-09-02 21:33:26] DEBUG[3240] res_pjsip_outbound_registration.c: Registration using newly created transport 0x75b18ef4

And no matter what in 13.22 all GVSIP trunks always showed "Registered"

After the 13.23 upgrade one of the GVSIP trunks showed "Rejected" so I issued "pjsip send register gvsipX"

The log showed:

[2018-09-10 22:31:29] NOTICE[15960] res_stun_monitor.c: Old external address/port 0.0.0.0:0 now seen as 10.10.10.10.1:17522.
[2018-09-10 22:31:34] WARNING[15948] res_pjsip_outbound_registration.c: No response received from 'sip:obihai.sip.google.com' on registration attempt to 'sip:[email protected]', retrying in '60'
[2018-09-10 22:32:19] DEBUG[15948] res_pjsip_outbound_registration.c: Registration re-using transport 0x76042cac
[2018-09-10 22:32:20] WARNING[15947] pjproject:                    SSL 6 [SSL_ERROR_ZERO_RETURN] (Read) ret: 0 len: 32000
[2018-09-10 22:32:25] DEBUG[15948] res_pjsip_outbound_registration.c: Registration using newly created transport 0x7604aeb4
[2018-09-10 22:32:25] DEBUG[15948] res_pjsip_outbound_registration.c: Stored service-route: <sip:ACAH...VH:5060;uri-econt=5FSPR673RW..MYI

And all I see ever after are the happy sequences like this:

[2018-09-10 23:29:45] DEBUG[20891] res_pjsip_outbound_registration.c: Stored service-route: <sip:ABZ...BVYIV:5060;transport=udp;lr;uri-econt=ZUGQBPSTW>
[2018-09-10 23:29:45] DEBUG[20891] res_pjsip_outbound_registration.c: Stored associated uri: <sip:[email protected]>P-Associated-URI<90>RQ^B0IQ^B
[2018-09-10 23:30:41] DEBUG[20891] res_pjsip_outbound_registration.c: Registration re-using transport 0x24eb28c
[2018-09-10 23:30:41] DEBUG[20891] res_pjsip_outbound_registration.c: Stored service-route: <sip:ACAH...W25:5060;uri-econt=5O6...4FTA;lr>Service-Route

Good to know. This is back burner for us, but maybe will try this weekend.

 

[jerrm]

gvsip-naf.patch was present in /usr/src

The patch version bundled in Ward's Asterisk 13.22 based http://incrediblepbx.com/gvsip-naf-gui.tar.gz or did you pull it down fresh from github?

 

[Vladimir Mikhelson]

The patch version bundled in Ward's Asterisk 13.22 based http://incrediblepbx.com/gvsip-naf-gui.tar.gz or did you pull it down fresh from github?

Just re-used the one which came with 13.22 Pi image from Ward, incrediblepbx13-raspbian8-gvsip.img
.

 

[Vladimir Mikhelson]

Bad news. GVSIP registrations do not survive a short Internet access outage in 13.23. By short I mean 65 seconds, the time it took my border gateway to reboot.

SIP and IAX produced the following messages after the access was restored:

 SIP, got a network change message, renewing all SIP registrations.
 IAX, got a network change message, renewing all IAX registrations.

Whereas PJSIP produced the following message nine (9) times, the number of my GVSIP trunks:

[2018-09-12 21:27:15] DEBUG[21801]: res_pjsip.c:2546 ast_sip_set_transport_from_endpoint_override: Transport override set!

And then this one about 100 times:

[2018-09-12 21:27:15] ERROR[15947]: res_pjsip_outbound_registration.c:590 stateless_send_resolver_callback: Resolver failed. Cannot send message

Fifty (50) minutes later all GVSIP trunks were "Unregistered"

 gvsip1/sip:obihai.sip.google.com                        gvsip1            Unregistered  
 gvsip2/sip:obihai.sip.google.com                        gvsip2            Unregistered  
 gvsip3/sip:obihai.sip.google.com                        gvsip3            Unregistered  
 gvsip4/sip:obihai.sip.google.com                        gvsip4            Unregistered  
 gvsip5/sip:obihai.sip.google.com                        gvsip5            Unregistered  
 gvsip6/sip:obihai.sip.google.com                        gvsip6            Unregistered  
 gvsip7/sip:obihai.sip.google.com                        gvsip7            Unregistered  
 gvsip8/sip:obihai.sip.google.com                        gvsip8            Unregistered  
 gvsip9/sip:obihai.sip.google.com                        gvsip9            Unregistered

After I issued nine (9) "pjsip send register gvsipX" all registrations showed "Rejected", but eventually they all changed to "Registered" except for one trunk for which I needed to send the register request several times.

 

[jerrm]

Had some time last night, so compiled 13.23. Will post how things go.

@wardmundy - I did this without the SRTP patch (didn't need it here), but are there any updates on that front?