Just for clarity sake, the problem I am having is that the assigned BLF line doesn't light up.
##### Begin Trace #####
U 2.XX.XX.187:6072 ->
10.22.110.11:5060REGISTER sip:
test.mydomain.com:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK172500819.
From: "302" <
sip:302@test.mydomain.com>;tag=1371858689.
To: "302" <
sip:302@test.mydomain.com>.
Call-ID:
259369610@192.168.1.138.
CSeq: 1 REGISTER.
Contact: <
sip:302@192.168.1.138:6072>.
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE.
Max-Forwards: 70.
User-Agent: Yealink SIP-T20P 9.72.0.30.
Expires: 300.
Allow-Events: talk,hold,conference,refer,check-sync.
Content-Length: 0.
.
U
10.22.110.11:5060 -> 2.XX.XX.187:6072
SIP/2.0 401 Unauthorized.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK172500819;rport=6072;received=2.XX.XX.187.
From: "302" <
sip:302@test.mydomain.com>;tag=1371858689.
To: "302" <
sip:302@test.mydomain.com>;tag=ff6b32c6b28b8954915484dd79f46b1c.f566.
Call-ID:
259369610@192.168.1.138.
CSeq: 1 REGISTER.
WWW-Authenticate: Digest realm="
test.mydomain.com", nonce="U2IkbVNiI0HW+fUAtRSaP0lh9eyQTQxV".
Server: kamailio (4.0.6 (x86_64/linux)).
Content-Length: 0.
.
U 2.XX.XX.187:6072 ->
10.22.110.11:5060REGISTER sip:
test.mydomain.com:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK215028252.
From: "302" <
sip:302@test.mydomain.com>;tag=1371858689.
To: "302" <
sip:302@test.mydomain.com>.
Call-ID:
259369610@192.168.1.138.
CSeq: 2 REGISTER.
Contact: <
sip:302@192.168.1.138:6072>.
Authorization: Digest username="302", realm="
test.mydomain.com", nonce="U2IkbVNiI0HW+fUAtRSaP0lh9eyQTQxV", uri="sip:
test.mydomain.com:5060", response="c1dd7e1c2e87d5274cff0ce18ca7c584", algorithm=MD5.
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE.
Max-Forwards: 70.
User-Agent: Yealink SIP-T20P 9.72.0.30.
Expires: 300.
Allow-Events: talk,hold,conference,refer,check-sync.
Content-Length: 0.
.
U
10.22.110.11:5060 -> 2.XX.XX.187:6072
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK215028252;rport=6072;received=2.XX.XX.187.
From: "302" <
sip:302@test.mydomain.com>;tag=1371858689.
To: "302" <
sip:302@test.mydomain.com>;tag=ff6b32c6b28b8954915484dd79f46b1c.fe72.
Call-ID:
259369610@192.168.1.138.
CSeq: 2 REGISTER.
Contact: <
sip:302@192.168.1.138:6072>;expires=300;received="sip:2.XX.XX.187:6072".
Server: kamailio (4.0.6 (x86_64/linux)).
Content-Length: 0.
.
U 2.XX.XX.187:6072 ->
10.22.110.11:5060SUBSCRIBE
sip:301@test.mydomain.com:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK148023404.
From: "302" <
sip:302@test.mydomain.com>;tag=1972538712.
To: <
sip:301@test.mydomain.com>.
Call-ID:
1265783225@192.168.1.138.
CSeq: 1 SUBSCRIBE.
Contact: <
sip:302@192.168.1.138:6072>.
Accept: application/dialog-info+xml.
Max-Forwards: 70.
User-Agent: Yealink SIP-T20P 9.72.0.30.
Expires: 1800.
Event: dialog.
Content-Length: 0.
.
U
10.22.110.11:5060 -> 2.XX.XX.187:6072
SIP/2.0 407 Proxy Authentication Required.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK148023404;rport=6072;received=2.XX.XX.187.
From: "302" <
sip:302@test.mydomain.com>;tag=1972538712.
To: <
sip:301@test.mydomain.com>;tag=ff6b32c6b28b8954915484dd79f46b1c.4854.
Call-ID:
1265783225@192.168.1.138.
CSeq: 1 SUBSCRIBE.
Proxy-Authenticate: Digest realm="
test.mydomain.com", nonce="U2IkblNiI0KIkAF5hKzVFSna1K5la4z6".
Server: kamailio (4.0.6 (x86_64/linux)).
Content-Length: 0.
.
U 2.XX.XX.187:6072 ->
10.22.110.11:5060SUBSCRIBE
sip:301@test.mydomain.com:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK1849548150.
From: "302" <
sip:302@test.mydomain.com>;tag=1972538712.
To: <
sip:301@test.mydomain.com>.
Call-ID:
1265783225@192.168.1.138.
CSeq: 2 SUBSCRIBE.
Contact: <
sip:302@192.168.1.138:6072>.
Proxy-Authorization: Digest username="302", realm="
test.mydomain.com", nonce="U2IkblNiI0KIkAF5hKzVFSna1K5la4z6", uri="
sip:301@test.mydomain.com:5060", response="8f2af5fa7e15052dfd776834c759ee75", algorithm=MD5.
Accept: application/dialog-info+xml.
Max-Forwards: 70.
User-Agent: Yealink SIP-T20P 9.72.0.30.
Expires: 1800.
Event: dialog.
Content-Length: 0.
.
U
10.22.110.11:5060 -> 2.XX.XX.187:6072
SIP/2.0 405 Method Not Allowed.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK1849548150;rport=6072;received=2.XX.XX.187.
From: "302" <
sip:302@test.mydomain.com>;tag=1972538712.
To: <
sip:301@test.mydomain.com>;tag=0da20c9505477b656ed669e756e303a0-bd1c.
Call-ID:
1265783225@192.168.1.138.
CSeq: 2 SUBSCRIBE.
Server: kamailio (4.0.6 (x86_64/linux)).
Content-Length: 0.
.
U
10.22.110.11:5060 -> 2.XX.XX.187:6062
....
U 2.XX.XX.187:6072 ->
10.22.110.11:5060
REGISTER sip:
test.mydomain.com:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK1251189297.
From: "302" <
sip:302@test.mydomain.com>;tag=1371858689.
To: "302" <
sip:302@test.mydomain.com>.
Call-ID:
259369610@192.168.1.138.
CSeq: 3 REGISTER.
Contact: <
sip:302@192.168.1.138:6072>.
Authorization: Digest username="302", realm="
test.mydomain.com", nonce="U2IkbVNiI0HW+fUAtRSaP0lh9eyQTQxV", uri="sip:
test.mydomain.com:5060", response="c1dd7e1c2e87d5274cff0ce18ca7c584", algorithm=MD5.
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE.
Max-Forwards: 70.
User-Agent: Yealink SIP-T20P 9.72.0.30.
Expires: 300.
Allow-Events: talk,hold,conference,refer,check-sync.
Content-Length: 0.
.
U 2.XX.XX.187:6072 ->
10.22.110.11:5060.
.
U
10.22.110.11:5060 -> 2.XX.XX.187:6072
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.1.138:6072;branch=z9hG4bK1251189297;rport=6072;received=2.XX.XX.187.
From: "302" <
sip:302@test.mydomain.com>;tag=1371858689.
To: "302" <
sip:302@test.mydomain.com>;tag=ff6b32c6b28b8954915484dd79f46b1c.4e33.
Call-ID:
259369610@192.168.1.138.
CSeq: 3 REGISTER.
Contact: <
sip:302@192.168.1.138:6072>;expires=300;received="sip:2.XX.XX.187:6072".
Server: kamailio (4.0.6 (x86_64/linux)).
Content-Length: 0.
.
U
10.22.110.11:5060 -> 2.XX.XX.187:6072