PBXes (http://www1.pbxes.com/forum/index.php)
- English (http://www1.pbxes.com/forum/board.php?boardid=16)
-- Feature Requests (http://www1.pbxes.com/forum/board.php?boardid=23)
--- RE: Ext-local context issue: Incorrect trunk name in log used (provided by provider vs name from PBX (http://www1.pbxes.com/forum/threadid.php?threadid=1303806429)

Ext-local context issue: Incorrect trunk name in log used (provided by provider vs name from PBXes)

Hi,

i've got 2 SIP trunks from the same cellular provider, Megafon russia (Multifon). Both are incoming / outgoing.

In Trunks setup page, they have 2 distinct names.

The problem: when incoming calls are being answered through PBXes, it logs them as being received from "multifon.ru", rather than from the respective trunk name assigned in setup.

It's a problem because there's no way to find out from which trunk (i.e. which celllular number) the call went from. I guess with 3 or more trunks, the inconvinience would be even bigger.

is there a way to fix this and use the name assigned in PBXes setup for logging?

thank you.

RE: Ext-local context issue: Incorrect trunk name in log used (provided by provider vs name from PBX

The trunk name is merely a convenience, which allows us to name trunks with meaningful names.

In the CDRs the trunk name indicates via which trunk the specific outbound call was delivered through, since you can go and see which FQDN or IP you have specified in the trunk's setup.

But in the case of inbound calls, the Invite to PBXes' SIP Proxy can arrive from an IP or FQDN which is not the same or even close to the FQDN you have specified in the trunk setup. As such, the trunk name in the CDRs of inbound calls displays the Reverse DNS name of the SIP Proxy which initiated the inbound call to PBXes.

So this is not a bug but a well-thought out compromise, for a less than perfect situation.

Of course you can suggest the implementation of a feature which partly matches FQDNs to RDNS names, so I will move this thread to the appropriate sub-forum.

RE: Ext-local context issue: Incorrect trunk name in log used (provided by provider vs name from PBX

thank you!