Configuration
Every setting in Avaya IP Office SMDR Connector, and what each one changes.
Settings → Avaya Telephony
| Setting | Default | What it changes |
|---|---|---|
| Phone match digits | 9 | Trailing digits that must agree for a call to match a contact |
| Archive calls after | 0 (off) | Hides old calls from the default view, keeps them |
| Delete calls after | 0 (off) | Permanently deletes |
| Keep request log for | 30 days | How long webhook audit rows are kept |
Phone match digits
Nine suits Egypt: it ignores the country code and any trunk prefix, so +20 100 123 4567, 0100 123 4567 and 1001234567 all match the same contact.
Raise it if your contacts are stored with country codes and you are getting false matches. Lower it — never below 6, which the field enforces — if your PBX adds a prefix that eats into the significant digits.
Changing it does not re-match existing calls. Select them and press Reprocess.
Deleting is off by default
Archiving hides; deleting destroys. Delete calls after ships as 0 because a call log is evidence — of a complaint, of a commitment, of who said what and when — and something that destroys evidence on a timer has to be chosen deliberately rather than inherited from a default.
Per endpoint
Telephony → Configuration → Endpoints. One per company.
| Setting | What it changes |
|---|---|
| IP allowlist | Which addresses may post. Empty means any. |
| Rate limit per minute | Caps how fast the listener may post |
| Batch cap / payload cap | Largest batch and body accepted |
| Store internal calls | Extension-to-extension calls, which are high volume |
| Missed calls create activities | A follow-up task on the matched contact |
| Missed calls create leads | A lead for a caller nobody recognises |
Token rotation
Rotating issues a new token and keeps the previous one working for a grace period, so you can restart the listener without losing records. The old token expires on its own.
Tokens are 32 random bytes, compared in constant time, masked in the interface and readable only by a Technical Administrator.
Missed-call leads
Off unless you want them. It creates a lead for an unmatched inbound caller — useful for a sales line, noise for a support line where the same unknown number calls six times.
Hunt-group calls are excluded from missed-call activities entirely: one ringing group produces one SMDR record per leg, and a task per leg is not a to-do list, it is a punishment.
Extensions
Telephony → Configuration → Extensions. Map a PBX extension to an Odoo user, and mark the ones that are hunt groups rather than people.
This is what turns extension 205 answered into a name on the call, and it is what the agent column and the per-user KPIs are built on. Without it calls are still logged; they just have no owner.
The scheduled actions
| Action | What it does |
|---|---|
| Avaya: re-match unmatched calls | Retries matching as contacts are added |
| Avaya: retry failed call processing | Picks up records that errored |
| Avaya: apply retention policy | Enforces the archive and delete windows |
The first is why a call that arrived before its contact existed does not stay orphaned forever.
Listener settings
In the listener's .env:
| Variable | Notes |
|---|---|
| ODOO_WEBHOOK_URL | From Show Credentials |
| ODOO_WEBHOOK_TOKEN | Likewise |
| SMDR_PORT | Must match IP Office's TCP Port |
| PBX_UTC_OFFSET_MINUTES | The PBX clock's offset from UTC |
PBX_UTC_OFFSET_MINUTES deserves care
On IP Office releases that do not emit a unique call id, the id is synthesised from the timestamp. Changing this offset on a running system can therefore store calls either side of the change twice.
Change it during a quiet period — or, better, set the PBX clock to UTC and leave the offset at zero.