We have two Avaya IP Office PBX on different location and both are using similiar SIP trunk configuration and same service provider. Recently, we noticed a couple of SIP out of services on one of our IP Office in every week. By using sysmonitor, we found that PBX was sending one special OPTIONS message, which is totally different from the regular OPTIONS messages (default 30000 msecond interval) when we got SIP out of services. The message looks like below,
XXX.XXX.XXX.XXX - PROXY SERVER
YYY.YYY.YYY.YYY - PBX WAN INTERFACE
573433022mS SIP Reg/Opt Tx: 18
OPTIONS sip:Unknown@XXX.XXX.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;rport;branch=z9hG4bK0fe99a8780e5aa0329322c18db11116d
From: <sip:Unknown@XXX.XXX.XXX.XXX>;tag=f0072426ca6d1bc7
To: <sip:Unknown@XXX.XXX.XXX.XXX>
Call-ID: 4dc609c3e789f55d92b182d54ccb1798@YYY.YYY.YYY.YYY
CSeq: 2038199533 OPTIONS
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
Content-Length: 0
573433046mS SIP Reg/Opt Rx: 18
SIP/2.0 401 Unauthorized
Digest realm="edm.trk.tprm.ca ",nonce="d9cb374917d5",stale=false,algorithm=MD5,qop="auth"
Call-ID: 4dc609c3e789f55d92b182d54ccb1798@YYY.YYY.YYY.YYY
CSeq: 2038199533 OPTIONS
From: <sip:Unknown@XXX.XXX.XXX.XXX>;tag=f0072426ca6d1bc7
To: <sip:Unknown@XXX.XXX.XXX.XXX>;tag=ZZZ.ZZZ.ZZZ.ZZZ+1+3e3a27+b8e8b724
Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;received=YYY.YYY.YYY.YYY;rport=5060;branch=z9hG4bK0fe99a8780e5aa0329322c18db11116d
Server: DC-SIP/2.0
Organization: MetaSwitch
Supported: resource-priority, 100rel
Content-Length: 0
As seen from above, the response is 401 Unauthorized as Unknown@XXX.XXX.XXX.XXX couldn't get authorized on proxy server. However, the other PBX using almost exactly same configuration never sends this kind of OPTIONS messages. The most annoying thing is the PBX thinks SIP service is down when receives 401 error. At the same time, every out of service will cleared in 1 minute or so.
really appreciate any idea regarding this issue.
XXX.XXX.XXX.XXX - PROXY SERVER
YYY.YYY.YYY.YYY - PBX WAN INTERFACE
573433022mS SIP Reg/Opt Tx: 18
OPTIONS sip:Unknown@XXX.XXX.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;rport;branch=z9hG4bK0fe99a8780e5aa0329322c18db11116d
From: <sip:Unknown@XXX.XXX.XXX.XXX>;tag=f0072426ca6d1bc7
To: <sip:Unknown@XXX.XXX.XXX.XXX>
Call-ID: 4dc609c3e789f55d92b182d54ccb1798@YYY.YYY.YYY.YYY
CSeq: 2038199533 OPTIONS
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
Content-Length: 0
573433046mS SIP Reg/Opt Rx: 18
SIP/2.0 401 Unauthorized
Digest realm="edm.trk.tprm.ca ",nonce="d9cb374917d5",stale=false,algorithm=MD5,qop="auth"
Call-ID: 4dc609c3e789f55d92b182d54ccb1798@YYY.YYY.YYY.YYY
CSeq: 2038199533 OPTIONS
From: <sip:Unknown@XXX.XXX.XXX.XXX>;tag=f0072426ca6d1bc7
To: <sip:Unknown@XXX.XXX.XXX.XXX>;tag=ZZZ.ZZZ.ZZZ.ZZZ+1+3e3a27+b8e8b724
Via: SIP/2.0/UDP YYY.YYY.YYY.YYY:5060;received=YYY.YYY.YYY.YYY;rport=5060;branch=z9hG4bK0fe99a8780e5aa0329322c18db11116d
Server: DC-SIP/2.0
Organization: MetaSwitch
Supported: resource-priority, 100rel
Content-Length: 0
As seen from above, the response is 401 Unauthorized as Unknown@XXX.XXX.XXX.XXX couldn't get authorized on proxy server. However, the other PBX using almost exactly same configuration never sends this kind of OPTIONS messages. The most annoying thing is the PBX thinks SIP service is down when receives 401 error. At the same time, every out of service will cleared in 1 minute or so.
really appreciate any idea regarding this issue.