Recording which line/provider an inbound SMS arrived on

[DaveFF]

Hi everyone,

We're looking at getting a second Clickatell account, so we can have one number for surveys, and a separate number for non-bulk communication between certain contacts. When an inbound message arrives, we want to record which line it arrived on.

In the case of Clickatell, there is a 'to' field in the callback URL, which is not currently passed through to CRM_SMS_Provider::processInbound. If it was (which wouldn't be a huge change), we could then have a contact for each of our inbound numbers, and identify the line by which of these target contacts the activity gets attached to.

We'd rather record the line using the ID from the civicrm_sms_provider table (even if we need to determine it from the 'to' number). Is the ability to record the line/provider something the community would be interested in?

• A new field could be added to civicrm_activity. (I note that phone_id and phone_number are already there.) If it is determined based on the destination number, it may also be required to have a way of mapping the destination number to the civicrm_sms_provider entry. If this happened, would it most likely need to be targeted to 4.5, 4.6 or something further ahead? Could it also be generalised to other forms of communication?
• Add a custom field on the Inbound SMS activity type. Change CRM_SMS_Provider to fill it. Would custom fields be allowed in something contributed to core?
• Alternatively the custom field could be filled in a pre hook on the activity creation, perhaps based on the target contact as described above.
• If it isn't something the community is interested in, we'd probably go with option 2 (under custom PHP) or 3 (in an extension).

[sivani]

Hi everyone,

We're looking at getting a second Clickatell account, so we can have one number for surveys, and a separate number for non-bulk communication between certain contacts. When an inbound message arrives, we want to record which line it arrived on.

In the case of Clickatell, there is a 'to' field in the callback URL, which is not currently passed through to CRM_SMS_Provider::processInbound. If it was (which wouldn't be a huge change), we could then have a contact for each of our inbound numbers, and identify the line by which of these target contacts the activity gets attached to.

We'd rather record the line using the ID from the civicrm_sms_provider table (even if we need to determine it from the 'to' number). Is the ability to record the line/provider something the community would be interested in?

• A new field could be added to civicrm_activity. (I note that phone_id and phone_number are already there.) If it is determined based on the destination number, it may also be required to have a way of mapping the destination number to the civicrm_sms_provider entry. If this happened, would it most likely need to be targeted to 4.5, 4.6 or something further ahead? Could it also be generalised to other forms of communication?
• Add a custom field on the Inbound SMS activity type. Change CRM_SMS_Provider to fill it. Would custom fields be allowed in something contributed to core?
• Alternatively the custom field could be filled in a pre hook on the activity creation, perhaps based on the target contact as described above.
• If it isn't something the community is interested in, we'd probably go with option 2 (under custom PHP) or 3 (in an extension).

Hi,
  I am using clickatell civi extension in civicrm 4.4.6. I am using Drupal7 as cms. As sending sms is an activity in civicrm so i want to use sending sms activity in webform. In drupal (by using civicrm-webform integation) webform >> civicrm tab activity section outbound sms activity is there. How sending sms is working through Webform ?