provided by Star2Billing S.L.

Hi

I know the subject has been discussed here... but despite all the seach on the forum, I cant succeed in doing what I want.

I am setting up A2B to be a wholesale system. I will collect calls via SIP and terminate them either via DAHDI/SS7 or SIP.

I expect that users connecting to the system will be be IP-PBXes (or with a gateway).

My issues lie around caller_id propagation and remote party identification.

1. Remote party identification
I create the customer account in A2B - export as SIP friend - and program the customer pbx with the a2b USERNAME and secret code
Yet, that does not work when trying to call any number.
I need to either add host=ipofthecustomer to additional_a2billing_sip.conf
or add a fromuser=USERNAME in the customer original config (but it will not likely be asterisk boxes, so this does not seem very convenient - and I want the simplest setup for the customer)

2. Calling party propagation
in such scenario as describe in previous paragraph, the caller id is changed to the account number - however, I want to present the callerid of the original PBX !


Any help would be much appreciated !

J.

ok - regarding 2) - calling number propagation - just had to remove the "callerid" field in the additional_a2billing_sip.conf

so I am left with my issue 1)

how can I identify a remote pbx using username/password, and no static host ?

thanks for the help,

J.

thanks for the help,

my issue is when I set host=dynamic, I start to get "Forbidden" messages when I try to initiate a call from a remote pbx.

My understanding is that the remote extension is not known by Ast/A2b, and therefore, is rejected (unless I register first).

What puzzles me, is when I send a call to a Betamax provider for instance, they dont have my ip, I dont register, and yet, I send a correct sip messages that allows me to identified properly !

I'd like to reproduce this
J.

cerien:

i saw this issue as well when i recently set it up for wholesale. when using ip auth you will automatically register with the box. when using the dynamic ip try using a register string in the trunk to send the call. user:[email protected]

hope this helps.

also you will notice you can test with a client, like x-lite without any other settings. but when testing with another asterisk box you need to specify the reg string. or you can just do ip auth and wipe the user and pass form your host box.

Dear Team

I think there is addithional problem here!

When you send a call from the remote PBX as a wholesale client, you will found that the session opened in the remote SIP client, and if the call failed the remote PBX client will cost that call without talking.

if we apply these reules
exten => _X.,1,Answer
exten => _X.,n,Wait(1)
exten => _X.,n,DeadAGI(a2billing.php|1)
exten => _X.,n,Hangup

the call will open first(Answer)

and if you put it like that

exten => _X.,n,DeadAGI(a2billing.php|1)
exten => _X.,n,Hangup
the call will not go through

what is the solution!!


t

If I understand the issue correctly, most wholesale switches authenticate via IP and not user accounts. If you want to authenticate via IP, you need to have insecure=port,invite & and IP address of your client/provider in the host field. The username/secret should be erased. See the following post from the knowledgeable jroper:
viewtopic.php?f=21&t=6752&p=26486&hilit=wholesale+peer#p26486

Additionally, I experienced the same issue and also had to disable real-time (use_realtime = no) via the System Settings > Global List menu.

Hi

With port,invite the username is ignored, so can be left in place, however port,invite only works with peer type.

Joe

Interesting. Is this specific to A2? I could have sworn I was using type=friend in Asterisk with insecure=port,invite

No the settings in A2billing just populate sip.conf. I read that fact somewhere, cannot find the reference to it on voip info now though.

Joe

Maybe this is what you mean:
http://www.voip-info.org/wiki/view/Aste ... er+vs+peer

Just confirmed it on my own system though. Running Asterisk v 1.4.26 & have a number of entries defined as a friend & authenticating them based on IP.

Try it out! =)