Difference between revisions of "CallerID not passed"
From Kolmisoft Wiki
Jump to navigationJump to search
(New page: ==Problem== CallerID is empty or wrong on receiving end from MOR ==Troubleshooting== Make sure there're empty fields in Device's settings window CallerID section (Name/Number)) |
|||
| Line 6: | Line 6: | ||
Make sure there're empty fields in Device's settings window CallerID section (Name/Number) | Make sure there're empty fields in Device's settings window CallerID section (Name/Number) | ||
==TrixBox Trunk Troubleshooting== | |||
When passing multiple CallerIDs from multiple extensions in TrixBox through a single ANI-enabled trunk to MOR, make sure to define the outbound TrixBox PEER CallerID as empty using '''callerid="" <>'''. | |||
If you don't include this, your MOR trunk will publish whichever CallerID was last passed to it. This will not allow you to correctly track different users' CallerID in MOR to provide them with separate call cost tracking. | |||
Also, be sure NOT to define the inbound USER CalleID on the same TrixBox trunk with the same empty entry. If you do, the CallerID will be stripped from all incoming calls | |||
Latest revision as of 19:37, 18 February 2008
Problem
CallerID is empty or wrong on receiving end from MOR
Troubleshooting
Make sure there're empty fields in Device's settings window CallerID section (Name/Number)
TrixBox Trunk Troubleshooting
When passing multiple CallerIDs from multiple extensions in TrixBox through a single ANI-enabled trunk to MOR, make sure to define the outbound TrixBox PEER CallerID as empty using callerid="" <>.
If you don't include this, your MOR trunk will publish whichever CallerID was last passed to it. This will not allow you to correctly track different users' CallerID in MOR to provide them with separate call cost tracking.
Also, be sure NOT to define the inbound USER CalleID on the same TrixBox trunk with the same empty entry. If you do, the CallerID will be stripped from all incoming calls
