Aastra 9133i SUBSCRIBE 403 Forbidden

[Michael]

Perhapse some magic setting needs to be turned on in the Aastra but I don't see anything obvious. Any ideas?

 

#
U 74.135.77.234:50131 -> 198.88.216.101:5060
REGISTER sip:pbxnsip1.omnilec.com:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.3;branch=z9hG4bK06de288c1.
Max-Forwards: 70.
Content-Length: 0.
To: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>.
From: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=a7f20582fe0ddc3.
Call-ID: 1fc3202d5a16af33d0352fbdc818b477@192.168.1.3.
CSeq: 711850105 REGISTER.
Contact: 3096700575 <sip:5076@192.168.1.3>;expires=30.
Allow-Events: talk,hold,conference.
Allow:NOTIFY,REFER,OPTIONS,INVITE,ACK,CANCEL,BYE,INFO.
User-Agent: Aastra 9133i/1.4.1.1077 Brcm Callctrl/1.5.1.0 MxSF/v3.2.6.26.
.

#
U 198.88.216.101:5060 -> 74.135.77.234:50131
SIP/2.0 401 Authentication Required.
Via: SIP/2.0/UDP 192.168.1.3;branch=z9hG4bK06de288c1;rport=50131;received=74.135.77.234.
From: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=a7f20582fe0ddc3.
To: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=0f097ca8ac.
Call-ID: 1fc3202d5a16af33d0352fbdc818b477@192.168.1.3.
CSeq: 711850105 REGISTER.
User-Agent: pbxnsip-PBX/2.0.0.1610.
WWW-Authenticate: Digest realm="pbxnsip1.omnilec.com",nonce="1625cf3b5516174a1d5be571df5f1b73",domain="sip:pbxnsip1.omnilec.com:5060",stale=true,algorithm=MD5.
Content-Length: 0.
.

#
U 74.135.77.234:50131 -> 198.88.216.101:5060
REGISTER sip:pbxnsip1.omnilec.com:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.3;branch=z9hG4bK961f15bc8.
Max-Forwards: 70.
Content-Length: 0.
To: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>.
From: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=a7f20582fe0ddc3.
Call-ID: 1fc3202d5a16af33d0352fbdc818b477@192.168.1.3.
CSeq: 711850106 REGISTER.
Contact: 3096700575 <sip:5076@192.168.1.3>;expires=30.
Allow-Events: talk,hold,conference.
Allow:NOTIFY,REFER,OPTIONS,INVITE,ACK,CANCEL,BYE,INFO.
Authorization:Digest response="51ae1a31ec19c3d6dfaa50fed272a9c5",nonce="1625cf3b5516174a1d5be571df5f1b73",username="5076",realm="pbxnsip1.omnilec.com",algorithm=MD5,uri="sip:pbxnsip1.omnilec.com:5060".
User-Agent: Aastra 9133i/1.4.1.1077 Brcm Callctrl/1.5.1.0 MxSF/v3.2.6.26.
.

#
U 198.88.216.101:5060 -> 74.135.77.234:50131
SIP/2.0 200 Ok.
Via: SIP/2.0/UDP 192.168.1.3;branch=z9hG4bK961f15bc8;rport=50131;received=74.135.77.234.
From: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=a7f20582fe0ddc3.
To: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=0f097ca8ac.
Call-ID: 1fc3202d5a16af33d0352fbdc818b477@192.168.1.3.
CSeq: 711850106 REGISTER.
Contact: 3096700575 <sip:5076@192.168.1.3>;expires=30.
Content-Length: 0.
.

#
U 198.88.216.101:5060 -> 74.135.77.234:50131
SUBSCRIBE sip:5076@192.168.1.3 SIP/2.0.
Via: SIP/2.0/UDP 198.88.216.101:5060;branch=z9hG4bK-a81f17c742db330ffac7fb77ca447b98;rport.
From: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=0f097ca8ac.
To: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=a7f20582fe0ddc3.
Call-ID: 5hcx87ph@pbx.
CSeq: 17904 SUBSCRIBE.
Max-Forwards: 70.
Contact: <sip:198.88.216.101:5060>.
Event: dialog.
Expires: 3600.
Content-Length: 0.
.

#
U 74.135.77.234:50131 -> 198.88.216.101:5060
SIP/2.0 403 Forbidden.
Call-ID: 5hcx87ph@pbx.
CSeq: 17904 SUBSCRIBE.
From: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=0f097ca8ac.
To: 3096700575 <sip:5076@pbxnsip1.omnilec.com:5060>;tag=a7f20582fe0ddc3.
Via: SIP/2.0/UDP 198.88.216.101:5060;branch=z9hG4bK-a81f17c742db330ffac7fb77ca447b98;rport.
Content-Length: 0.
Contact: 3096700575 <sip:5076@192.168.1.3>.
User-Agent: Aastra 9133i/1.4.1.1077 Brcm Callctrl/1.5.1.0 MxSF/v3.2.6.26.
.

[Vodia PBX]

Well, the PBX tries to find out if the Aastra would notify the PBX when it goes off hook. Obviously it does not do that, as many other devices don't. It is not a real reason for concern, but if you go offhook with the phone, don't be surprised you don't see that event on the LED keys of other devices.