I wrote:
> Traces of the following message types with 79X1 phones
> would be handy:
> 82 start tone
> 83 Stop tone
> 85 Set ringer message
> 9A Clear display message
> 106 Close receive channel
> 111 Call state message
> I am also looking into:
> RECEIVED UNKNOWN MESSAGE TYPE: c
> RECEIVED UNKNOWN MESSAGE TYPE: 9 (I think this is a line request)
OK, I managed to get a proper protocol decoder added to my
closed-source sniffer. It looks like the new phones are
much pickier about the response packets.
1st up, the line_stat_res_message structure:
Current:
uint32_t lineNumber;
char lineDirNumber[24];
char lineDisplayName[42];
uint32_t space;
Problem:
Packet captures against CCM show that lineDisplayName
should be [24], and that 60 bytes of packet padding is
needed/used.
Working:
uint32_t lineNumber;
char lineDirNumber[24];
char lineDisplayName[24];
uint32_t space[15];
So now the device registers and collects all of the
proper settings. The phone still does not work, throwing
errors for each of the response messages listed above.
I suspect that the same root cause applies, so I'll study
the CCM captures.
These changes DO NOT appear to break the older phones.
Dan
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
