SIP Trunk Out of service

[Scott_A_Connor]

Hi All,

Having an issue with voicehost sip trunks on an IPO where the SIP trunk is registered but shows as out of service in the alarms in system status. Monitor shows that the register will expire. There are a few screen grabs below.
System is version 8.0.66

Any help would be appreciated.

 

[janni78]

You would need to get some Monitor logs of the REGISTER process, but any release before 9.1 isn't great with SIP trunks as it has limited features.

"Trying is the first step to failure..." - Homer

 

[derfloh]

Seems that provider answers with expires=30 but IPO re-registers every 60 seconds.

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[Scott_A_Connor]

I ran monitor with register ticked and got the following:

253725800mS SIP Reg/Opt Tx: 19
OPTIONS sip:st.sipconvergence.co.uk SIP/2.0
Via: SIP/2.0/UDP 92.207.81.94:5060;rport;branch=z9hG4bKf95c25b5c81a1dab560d5a4aa453f6fb
From: <sip:st.sipconvergence.co.uk>;tag=6a20bd52a8132255
To: <sip:st.sipconvergence.co.uk>
Call-ID: 261d04821c21f0ddca22ec61a926d742@92.207.81.94
CSeq: 2028498419 OPTIONS
Contact: <sip:92.207.81.94:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
Content-Length: 0

253725802mS SIP Reg/Opt Tx: 19
OPTIONS sip:st.sipconvergence.co.uk SIP/2.0
Via: SIP/2.0/UDP 92.207.81.94:5060;rport;branch=z9hG4bKe3a9954cd689434ff1d66b9321e90b59
From: <sip:st.sipconvergence.co.uk>;tag=af33ed3c194be799
To: <sip:st.sipconvergence.co.uk>
Call-ID: 3e7fee2b1af9e8f2114293325ee2c6f9@92.207.81.94
CSeq: 1144768647 OPTIONS
Contact: <sip:92.207.81.94:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
Content-Length: 0

253725843mS SIP Reg/Opt Rx: 19
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 92.207.81.94:5060;rport=5060;received=92.207.81.94;branch=z9hG4bKf95c25b5c81a1dab560d5a4aa453f6fb
Call-ID: 261d04821c21f0ddca22ec61a926d742@92.207.81.94
From: <sip:st.sipconvergence.co.uk>;tag=6a20bd52a8132255
To: <sip:st.sipconvergence.co.uk>;tag=z9hG4bKf95c25b5c81a1dab560d5a4aa453f6fb
CSeq: 2028498419 OPTIONS

http://WWW-Authenticate:

Digest realm="voicehost",nonce="1582536649/55992ac459d4de48141a8a6377089e27",opaque="5ed712b670819afd",algorithm=md5,qop="auth"
Server: VoiceHost V5
Content-Length: 0

253725851mS SIP Reg/Opt Rx: 19
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 92.207.81.94:5060;rport=5060;received=92.207.81.94;branch=z9hG4bKe3a9954cd689434ff1d66b9321e90b59
Call-ID: 3e7fee2b1af9e8f2114293325ee2c6f9@92.207.81.94
From: <sip:st.sipconvergence.co.uk>;tag=af33ed3c194be799
To: <sip:st.sipconvergence.co.uk>;tag=z9hG4bKe3a9954cd689434ff1d66b9321e90b59
CSeq: 1144768647 OPTIONS

http://WWW-Authenticate:

Digest realm="voicehost",nonce="1582536649/e66312d746e68669d56e4a3e4db07cdd",opaque="11a2e51315ec3828",algorithm=md5,qop="auth"
Server: VoiceHost V5
Content-Length: 0

258357375mS SIP Reg/Opt Tx: 19
REGISTER sip:st.sipconvergence.co.uk SIP/2.0
Via: SIP/2.0/UDP 92.207.81.94:5060;rport;branch=z9hG4bK119341e6cd47da6a2259c463bf6c9683
From: <sip:ST14077T002@st.sipconvergence.co.uk>;tag=1a072fd2246df7c1
To: <sip:ST14077T002@st.sipconvergence.co.uk>
Call-ID: f4bf410ea342047e873b5218605879f9@92.207.81.94
CSeq: 1142566353 REGISTER
Contact: "Unknown" <sip:ST14077T002@92.207.81.94:5060;transport=udp>
Expires: 59
Max-Forwards: 70
User-Agent: IP Office 8.0 (66)
Supported: timer
Content-Length: 0

258357418mS SIP Reg/Opt Rx: 19
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 92.207.81.94:5060;rport=5060;received=92.207.81.94;branch=z9hG4bK119341e6cd47da6a2259c463bf6c9683
Call-ID: f4bf410ea342047e873b5218605879f9@92.207.81.94
From: <sip:ST14077T002@st.sipconvergence.co.uk>;tag=1a072fd2246df7c1
To: <sip:ST14077T002@st.sipconvergence.co.uk>;tag=z9hG4bK119341e6cd47da6a2259c463bf6c9683
CSeq: 1142566353 REGISTER

http://WWW-Authenticate:

Digest realm="voicehost",nonce="1582541281/d40478fc90e5506359346b29356618e6",opaque="7dea45924223acbf",algorithm=md5,qop="auth"
Server: VoiceHost V5
Content-Length: 0

258357420mS SIP Reg/Opt Tx: 19
REGISTER sip:st.sipconvergence.co.uk SIP/2.0
Via: SIP/2.0/UDP 92.207.81.94:5060;rport;branch=z9hG4bK9737bec5060b47594bb6235387f4d81c
From: <sip:ST14077T002@st.sipconvergence.co.uk>;tag=1a072fd2246df7c1
To: <sip:ST14077T002@st.sipconvergence.co.uk>
Call-ID: f4bf410ea342047e873b5218605879f9@92.207.81.94
CSeq: 1142566354 REGISTER
Contact: "Unknown" <sip:ST14077T002@92.207.81.94:5060;transport=udp>
Expires: 59
Authorization: Digest username="ST14077T002",realm="voicehost",nonce="1582541281/d40478fc90e5506359346b29356618e6",response="c78e48febeb44dab490d1fe21622ef7c",uri="sip:st.sipconvergence.co.uk",algorithm=MD5,qop=auth,nc=00000001,cnonce=
"f17877845eb5c567a671",opaque="7dea45924223acbf"
Max-Forwards: 70
User-Agent: IP Office 8.0 (66)
Supported: timer
Content-Length: 0

258357529mS SIP Reg/Opt Rx: 19
SIP/2.0 200 OK
Via: SIP/2.0/UDP 92.207.81.94:5060;rport=5060;received=92.207.81.94;branch=z9hG4bK9737bec5060b47594bb6235387f4d81c
Call-ID: f4bf410ea342047e873b5218605879f9@92.207.81.94
From: <sip:ST14077T002@st.sipconvergence.co.uk>;tag=1a072fd2246df7c1
To: <sip:ST14077T002@st.sipconvergence.co.uk>;tag=z9hG4bK9737bec5060b47594bb6235387f4d81c
CSeq: 1142566354 REGISTER
Date: Mon, 24 Feb 2020 10:48:01 GMT
Contact: <sip:ST14077T002@92.207.81.94:5060>;expires=59
Expires: 60
Server: VoiceHost V5
Content-Length: 0

 

[MaximusBrian]

are you behind a firewall?

 

[Scott_A_Connor]

yes, the router does the firewall. Its a draytek router with firewall rules to allow the SIP SBC`s through. I did try disabling them for a short while but had no effect.

 

[bahmonkeys]

The Sip trunk looks good to me no errors, no authentication issues and transmits\receives perfectly.

The issue is the expiry of the registration on the Sip Line. There should be a registration expiry timer on the sip trunk, change this timer to 0 so it doesn't timeout and resend the registration.

 

[janni78]

You should not put the expire timer to 0, the timer is used to determine how long a registration is valid and default is 3600 seconds unless anything else is given.
On registered trunks you are supposed to renew the registration which starts to happen normally around half the expire time.

The trace shows a a valid registration, you need a trace of when this fails.
Also you're saying you have an SBC so you might wanna trace on that.

"Trying is the first step to failure..." - Homer

 

[Scott_A_Connor]

Hi Janni78

The system wont allow the expire time to be 0, has to be a value of 1 or above. The registration is fine, in system status it shows the trunk is registered all the time, but in the alarms the trunk is out of service, this keeps counting up, the frequency of how quickly it counts up depends on the expire timer mentioned, which as you say usually occurs around half way through the expire time. so if expire time is set to 5 minutes, around 2mins and 30 seconds i will get an out of service alarm.
The SBC`s i mentioned are the SIP providers SBC`s, ive allowed them through the firewall. Although im confident the draytek is not effecting this, as i have disabled the firewall for a day to test and the error stays.

Thanks for the suggestions guys.

 

[janni78]

Do you have any issues with calls or is it just giving alarms?

It might just be a software issue, 8.0 66 was released in 2013 and a lot has happened with the SIP trunk feature of IP Office since then, personally I wouldn't run any system with SIP trunks below release 9.

"Trying is the first step to failure..." - Homer