Aastra sent me an automated response to my support ticket.  It just said.

Of course, it does not tell me what part it does not like ;-)  I have been 
unable to find any published specs for the Broadworks format.  I just see other 
phone vendors also list Broadworks format for their BLF list feature...ie 
polycom.  I wonder where the phone vendors are getting their Broadsoft specs 
from.


Incorrect state from list server:
<<<<<<<<<<=====IN=====192.168.15.253: Received SIP packet from: 192.168.15.40  
SIP/2.0 202 Accepted  From: "trisha white" 
<sip:2...@cleanburn.local>;tag=0852225ca8  To: "" 
<sip:~~rl...@cleanburn.local>;tag=36a9f9ac  Call-Id: 34e9545cec2a8ab2  Cseq: 
28150 SUBSCRIBE  Via: SIP/2.0/UDP 
192.168.15.253:5060;branch=z9hG4bK420390e9ca7a6469e  Expires: 3600  Contact: 
sip:~~rl...@192.168.15.40:5140  Date: Tue, 06 Jan 2009 21:14:14 GMT  Allow: 
INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, SUBSCRIBE, MESSAGE  User-Agent: 
sipXecs/3.10.2 sipXecs/rls (Linux)  Accept-Language: en  Supported: eventlist  
Content-Length: 0    <<<<<<<<<<=====IN=====END SIP packet   
mac:00-08-5D-1B-BD-05
Jan  6 16:18:33 192.168.15.253 00:00:25.530000 LogRawData: (SIP) INFO:   
<<<<<<<<<<=====IN=====192.168.15.253: Received SIP packet from: 192.168.15.40  
NOTIFY sip:2...@192.168.15.253:5060;transport=udp SIP/2.0  From: 
""<sip:~~rl...@cleanburn.local>;tag=36a9f9ac  To: "trisha 
white"<sip:2...@cleanburn.local>;tag=0852225ca8  Cseq: 1 NOTIFY  Call-Id: 
34e9545cec2a8ab2  Event: dialog  Subscription-State: active;expires=3600  
Content-Type: 
multipart/related;type="application/rlmi+xml";start="<r...@cleanburn.local>";boundary="fa54af06"
  Contact: sip:~~rl...@192.168.15.40:5140  Date: Tue, 06 Jan 2009 21:14:14 GMT  
Max-Forwards: 20  User-Agent: sipXecs/3.10.2 sipXecs/rls (Linux)  
Accept-Language: en  Supported: eventlist  Via: SIP/2.0/UDP 
192.168.15.40:5140;branch=z9hG4bK-sipXecs-001feb41135370844a850912289657d88c74  
Content-Length: 852    --fa54af06  CONTENT-ID: <0...@cleanburn.local>  
CONTENT-TYPE: application/dialog-info+xml  CONTENT-TRANSFER-ENCODING: binary    
<?xml version="1.0" encoding="UTF-8"?> <dialog-info 
xmlns="urn:ietf:params:xml:ns:dialog-info" version="3" state="full" 
entity="sip:2...@cleanburn.local">  sip:2...@cleanburn.local  </dialog-info>   
--fa54af06  CONTENT-ID: <r...@cleanburn.local>  CONTENT-TYPE: 
application/rlmi+xml  CONTENT-TRANSFER-ENCODING: binary    <?xml 
version="1.0"?>  
NaN.               --fa54af06--  <<<<<<<<<<=====IN=====END SIP packet   
mac:00-08-5D-1B-BD-05

>>> "Dale Worley" <dwor...@nortel.com> 01/06/09 10:12 AM >>>
On Mon, 2009-01-05 at 19:14 -0500, Matt White wrote:
> The admin manual states the BLF/List feature is complaint with the
> Broadworks format R11 and up.

Does it suggest that there is any documentation regarding the Broadworks
format?

Dale



_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users

Reply via email to