Hi Denis, Happy New Year. Apologies for the late response, I was in holiday mode.
Happy New Year too. Thank you for your helpful answer. So far, all modems on this planet have honored the default properly... > Sorry for my misunderstanding. I should have read the RFC better but this aspect is defined properly only in the following clause - "The Configuration Option is used to inform the peer which control characters MUST remain mapped when the peer sends them." So I have managed to find this after your message. Thank you. > So you have two options for fixing this: > - Make GAtPPP negotiate a default ACCM in all cases - Override the negotiated ACCM (using g_at_hdlc_set_recv_accm for your > particular modem. I think that this modem is buggy as you have clearly shown. I agree that it is not a good idea to do something which does not follow the RFCs fine. But, I feel that the default value for ACCM is not that one we should use. Excuse me if I am too direct here, I am not an expert in this field but I think it is better for DTE to send a configuration request with ACCM = 0x00000000 as pppd does because this allows us to send more information in the same number of bytes. Would you agree? If not I will override the negotiated ACCM, if it is left default, for this chinese modem because I do not feel that they could update the firmware to fulfill the RFC requirements in a reasonable amount of time if they even would. I do not think that they would even find this necessary if I had told them. Thank you very much for your help and sorry for bad patches. I will fix them soon. Have a great day. Regards, Sergei.
_______________________________________________ ofono mailing list -- [email protected] To unsubscribe send an email to [email protected]
