jroper wrote:
Hi
If for instance you are configuring FreePBX to connect to A2Billing, you do not want or need the fromuser directive, for reasons that you have discovered.
A working config for FreePBX will be something like:-
Peer Details
host=youra2bhostname
username=123456789
secret=987654321
type=peer
qualify=yes
trustrpid=yes
sendrpid=yes
User Context = 123456789
User Details
secret=987654321
type=user
context=from-trunk
Register String:123456789:987654321@youra2bhostname
That will allow calls inbound and outbound for the IAX protocol, I've not tested with SIP for inbound, but the outbound will work.
Modify this to suit your particular brand of IP PBX.
Joe
Hi Joe,
Many thanks for ur time!
I tried what you said, even though you mentioned that you have tested the incoming and outgoing for IAX2 and not SIP, I tried them on both protocols and on both out/in calls.
Here is the result:
With SIP, wthout fromuser field in the voip-settings in a2billing, the calls won't go out, and basically, authentication of peer is not being handled properly, so there must be fromuser=acountcode on both trunk setting of PBX, and voip-settings of a2billing.
With IAX2, I tried it without fromuser in the trunk settings, and the calls work and incoming won't show that account code anymore. I think is all about the INBOUND DID (destination, which in my PBX case, I have: SIP or IAX /ACCOUNT_CODE/DID) of callee, and that is exactly where my problem is, calls which come in shows the account code of the account being called to IF THE PROTOCOL IS SIP FOR INBOUND. My only guess is the destination I'm using, somehow, that ACCOUNT_CODE there is being picked as the number.
So, let me rephrase my question, is there anyway to fix this issue with SIP? I am using IAX2 trunking with the same account going to another fax server, so for me it is essential to use SIP, because that is how I go to my PBX server to handle the incoming call. Any idea?