Customer Specific Headers

[koolandrew]

I was wondering how to do this for the trunk or dial plan. We using asterisk for billing, and our current non-fusion pbx sends a customer specific header "GROUP_NAME: customer.domain" from the outbound trunk so we can identify which customer is calling and bill appropriately.

Any suggestions would be greatly appreciated.

 

[Adrian Fretwell]

In your outbound route, you can set a SIP header using the syntax sip_h_<name> for example:

 

[koolandrew]

Hi Adrian,

Thanks for the update. I will try to do so. The dial plan is a bit confusing as it creates two entries and no mention of the gateways. I see that there is already an entry for account code, so i will try and edit it. Thanks again for the quick reply.

 

[koolandrew]

Actually i have just noticed that the formatting is a little different. sip_h_X-accountcode=${accountcode}, so would you recommend ${mycustomer} or simply mycustomer.

 

[ad5ou]

The format depends on how/where you are getting the data. ${accountcode} is a variable and is replaced with whatever is entered in the accountcode field of the user making the call. This field would need to be entered in every user and could leave room for error.

If your variable isn't set elsewhere ie: a static assignment, the format Adrian shows would be correct. This would require a dedicated outbound route or at least extra dial plan for each tenant to set correct value but allows the value to be anything needed to match up in billing software.

Another example would be to use sip_h_X-accountcode=${domain_name} if your Fusion domain names match up correctly in your billing software.

 

[koolandrew]

Thanks for all your input. I tried all the suggestions, along with other info that i had read on other messages in this forum and outside of it.
Unfortunately, none of this information gets passed to the asterisk gw in a format that can be read by it, as when i do a debug, i dont see any of this info being passed over to the asterisk........, except for prefix. We have accounts codes that equal customer specific names, so we can send them as a prefix and they get authenticated. I realized this after i had tried everything else.
Thanks for all your help but i couldnt get it work other than this way but it is six of one, half of another as it turns out.

 

[dbbrito]

Hello koolandrew!
I'm also looking for a way to charge calls in another billing, astpp, a2billing, but nothing yet...., or did you manage to specify it in the headers? Thanks

 

[koolandrew]

Hi dbbrita, as mentioned in my last post, i could not get it to work; however, prefix did work and i used that. For our system prefix=account specific header, so it works. We lucked out.

 

[dbbrito]

Hi dbbrita, as mentioned in my last post, i could not get it to work; however, prefix did work and i used that. For our system prefix=account specific header, so it works. We lucked out.

But what billing are you using? How did you manage to integrate billing with fusion? thank you so much

 

[koolandrew]

We are using our own custom billing solution that was designed for other pbx platforms but works with this since we are using prefixs.

 

[dbbrito]

We are using our own custom billing solution that was designed for other pbx platforms but works with this since we are using prefixs.

Interested in selling this billing? can you give me more details?

 

[koolandrew]

it is written over many years but 99% complete as of recent. It does billing for a service provider, not just voip. It is pretty comprehensive, but you cannot compare to asttp and those other freebie ones...as i gave up on them almost immediately upon trying. Regarding voip, we can do provisioning, create plans, bill long distance, sms etc.

 

[dbbrito]

it is written over many years but 99% complete as of recent. It does billing for a service provider, not just voip. It is pretty comprehensive, but you cannot compare to asttp and those other freebie ones...as i gave up on them almost immediately upon trying. Regarding voip, we can do provisioning, create plans, bill long distance, sms etc.

For each fusion account do you create a trunk in the billing system?

 

[koolandrew]

When you say account, i believe you pbx instance, and we create a new account for each pbx or sometimes one customer might have more than one. In any case, it is referenced in a series of ways, but they are billed separately.