PBXes (http://www1.pbxes.com/forum/index.php)
- English (http://www1.pbxes.com/forum/board.php?boardid=16)
-- Bugs (http://www1.pbxes.com/forum/board.php?boardid=24)
--- Callthru issue w/ ClouFON (http://www1.pbxes.com/forum/threadid.php?threadid=1737221493)

Callthru issue w/ ClouFON

Hello,

I've encountered an issue with a DID from ClouFON, which I think is a bug (that I was able to find a workaround for), but I wanted to record it both for future reference if anyone else encounters the same issue and on the chance that it's actually a bug and can be resolved.

So, when you add a trunk that has its own DID from ClouFON, you can receive calls just fine. But existing trunk-less inbound callthru routes (that normally does work for other providers, e.g. Fonial) does not work for some reason. What I mean by trunk-less inbound callthru routes are inbound routes, that define a caller ID but not a trunk name, and has Callthru PIN activated.

I've tried to both check the logs and SIP trace but unfortunately couldn't get to something decisive; after the capability exchange the call abruptly gets hung up. On the contrary for a normal call (that is supposed to be routed to somewhere somehow) after the capability exchange everything works fine and the destination in fact receives the call.

After a while of bruteforce trying of different configuration combinations I can think of, the solution I found was to create new extra inbound callthru routes that define the trunk name as the ClouFON trunk username and caller ID as normal in addition to the existing inbound callthru routes. With that setup somehow it started to work.

I consider this as a bug because in my mind (and from the explanation on the new inbound route creation page) leaving the trunk name empty should match all trunks no matter what, which does not happen in this case. My problem is solved (hopefully for good), but if you'd want to resolve it @i-p happy to help.

Best,
Berkay

RE: Callthru issue w/ ClouFON

Do you have other trunks working with inbound routes having
- an empty trunk name
- just a caller ID starting with "+"?

RE: Callthru issue w/ ClouFON

Zitat:

Originally posted by i-p Do you have other trunks working with inbound routes having - an empty trunk name - just a caller ID starting with "+"?

Yes, I always had these inbound routes working with another trunk (namely Fonial).