Hi all, I have re-organized the internals of the DLR processing a bit to make the DLR proxying accross different SMSC modules more transparent.
Basicaly what has changed is that another parameter is given to dlr.c:dlr_add() call which contains the source of the message. Accoding to this the gw/smsc/smsc_foobar.c modules had to be addopted. The most important change is between gw/dlr.c and gw/urlttrans.c where the DLR URL is extracted. dlr_find() now sets the DLR URL within the msg->sms.dlr_url variable and leaves msg->sms.msgdata free to be populated by the smsc module on it's own. The pattern function in urltrans.c graps the URL to be triggered for the DLR from the msg->sms.dlr_url variable rather then parsing the msg->sms.msgdata on it's own. I'd like to request anyone who is using the DLR functions within the varios mudules to confirm that the current change has not broken anything. At least I have tested this for EMI2 and SMPP. Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 40470 D�sseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
