Howto:Busy lamp field (partner keys) with SIP phones

Applies To

This information applies to

• innovaphone PBX, v6
• SIP phones supporting "Dialog Package" according to RFC-4235

More Information

Problem Details

   SUBSCRIBE sip:211@172.16.16.180;user=phone SIP/2.0
   Via: SIP/2.0/UDP 172.16.16.34:1346;branch=z9hG4bK-ayuayllwo4ql;rport
   From: <sip:snom@172.16.16.180>;tag=mynrfel9vl
   To: <sip:211@172.16.16.180;user=phone>
   Call-ID: dedccb476ac9-47x5gchyicsw@snomSoft-000413FFFFFF
   CSeq: 1 SUBSCRIBE
   Max-Forwards: 70
   Contact: <sip:snom@172.16.16.34:1346;line=ojn9itpa>;flow-id=1
   Event: dialog
   Accept: application/dialog-info+xml
   Expires: 3600
   Content-Length: 0

   SIP/2.0 200 OK
   Via: SIP/2.0/UDP 172.16.16.34:1346;branch=z9hG4bK-ayuayllwo4ql;rport
   From: <sip:snom@172.16.16.180>;tag=mynrfel9vl
   To: <sip:211@172.16.16.180;user=phone>;tag=2870352540
   Call-ID: dedccb476ac9-47x5gchyicsw@snomSoft-000413FFFFFF
   CSeq: 1 SUBSCRIBE
   Content-Length: 0
   Expires: 360
   Server: (innovaphone IP3000/6.00 dvl-sr2 [06-60913.tac/322/106])

   NOTIFY sip:snom@172.16.16.34:1346;line=ojn9itpa SIP/2.0
   Via: SIP/2.0/UDP 172.16.16.180:5060;branch=z9hG4bK-31170C90;rport
   From: <sip:207@172.16.16.180;user=phone>;tag=2870352458
   To: <sip:snom@172.16.16.180>;tag=kxndmxevob
   Call-ID: 19dbcb47a4e9-2wgz8leeajhj@snomSoft-000413FFFFFF
   CSeq: 261 NOTIFY
   Contact: <sip:207@172.16.16.180;user=phone>
   Content-Length: 348
   Content-Type: application/dialog-info+xml
   Max-Forwards: 70
   Event: dialog
   Subscription-State: active

   <?xml version="1.0"?>
   <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" state="full" version="5">
       <dialog id="1" direction="initiator" call-id="19990635e909d3118b210090330200d6">
           <state>proceeding</state>
           <local>
               <identity>sip:207@172.16.16.180</identity>
           </local>
           <remote>
               <identity>sip:211@172.16.16.180</identity>
           </remote>
       </dialog>
   </dialog-info>


   SIP/2.0 200 Ok
   Via: SIP/2.0/UDP 172.16.16.180:5060;branch=z9hG4bK-31170C90;rport=5060
   From: <sip:207@172.16.16.180;user=phone>;tag=2870352458
   To: <sip:snom@172.16.16.180>;tag=kxndmxevob
   Call-ID: 19dbcb47a4e9-2wgz8leeajhj@snomSoft-000413FFFFFF
   CSeq: 261 NOTIFY
   Content-Length: 0

   NOTIFY sip:snom@172.16.16.34:1346;line=ojn9itpa SIP/2.0
   Via: SIP/2.0/UDP 172.16.16.180:5060;branch=z9hG4bK-31170C92;rport
   From: <sip:207@172.16.16.180;user=phone>;tag=2870352458
   To: <sip:snom@172.16.16.180>;tag=kxndmxevob
   Call-ID: 19dbcb47a4e9-2wgz8leeajhj@snomSoft-000413FFFFFF
   CSeq: 263 NOTIFY
   Contact: <sip:207@172.16.16.180;user=phone>
   Content-Length: 348
   Content-Type: application/dialog-info+xml
   Max-Forwards: 70
   Event: dialog
   Subscription-State: active

   <?xml version="1.0"?>
   <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" state="full" version="6">
       <dialog id="1" direction="initiator" call-id="19990635e909d3118b210090330200d6">
           <state>terminated</state>
           <local>
               <identity>sip:207@172.16.16.180</identity>
           </local>
           <remote>
               <identity>sip:211@172.16.16.180</identity>
           </remote>
       </dialog>
   </dialog-info>


   SIP/2.0 200 Ok
   Via: SIP/2.0/UDP 172.16.16.180:5060;branch=z9hG4bK-31170C92;rport=5060
   From: <sip:207@172.16.16.180;user=phone>;tag=2870352458
   To: <sip:snom@172.16.16.180>;tag=kxndmxevob
   Call-ID: 19dbcb47a4e9-2wgz8leeajhj@snomSoft-000413FFFFFF
   CSeq: 263 NOTIFY
   Content-Length: 0