Simple CDRs w/Asterisk/OpenSER.

2 msg	Missing TRANSFER event in queue log when usingL...
2 msg	sounds
3 msg	Re: Determining the used codec for the IP Trunk...
5 msg	Call Queues
2 msg	sometimes half audio on 7960
4 msg	Call Screening Not Working
1 msg	IAX-Voicemail
2 msg	IAX additional call-data
1 msg	Visually impaired employees

Simple CDRs w/Asterisk/OpenSER.
\ Alex Balashov (5 Jul 2007)
. \ Jaswinder Singh (5 Jul 2007)

6 msg	REGEX expression for NXXNXXXXXX?
1 msg	Re: exits in NJ
1 msg	connecting 1.2 and 1.4 using SIP
2 msg	SIP / STUN / Network - Help!!
4 msg	G729 on Solaris SPARC/x86/x64 Codec
1 msg	Process not draining UDP Recv-Q on port 5060
4 msg	sometimes calls drop during attended transfer
3 msg	Asterisk E1 card support Q.SIG
1 msg	Re: AgentCallBackLogin vsAddQueueMember
1 msg	Re: AgentCallBackLogin vs AddQueueMember

Subject:	Simple CDRs w/Asterisk/OpenSER.
Group:	Asterisk-users
From:	Alex Balashov
Date:	5 Jul 2007

Suggestions on how to use Asterisk to collect CDRs from a OpenSER-based
proxy / call routing setup? I need to get simple CDRs; not for detailed
settlement/rating, but just for reconciliation with an ultimate TDM
carrier just to make sure we only get billed for what we're actually
using.

I'd use the often-heralded approach of dumping a call from OpenSER into
Asterisk and having it bounce right back out toward the proxy by way of
REINVITEs. I don't want the media running through Asterisk or Asterisk
being a limiting factor in that regard.

The problem is I don't have native G.729 support - we have no need for
it because neither the customer's network elements nor ours lack an
implementation of their own they can negotiate on just fine. But
unfortunately Asterisk insists on natively homogenising the SDP from
both sides even if it subsequently removes itself from the media path!

So, I end up with situations where on the one side, I get, say:

Customer MGW --> OpenSER --> Asterisk - sends call as G.729.

Asterisk --> OpenSER --> Our MGW - our MGW prefers G.711a.

Now, if customer MGW <-> Our MGW were talking directly, as they do
when the deal is brokered through the OpenSER proxy, they would simply
negotiate upon what they agree. But for some reason with Asterisk
this does not seem to be working as advertised; we get lots of failed
calls if we pass them through Asterisk because one leg is one codec
and the other is another. I am not sure how it arrives at that
conclusion despite the overlap of shared codecs (G.729 on both sides,
I would expect it to pass thru licence-free), and to be honest, I
don't particularly care if it's a bug or a feature, I just need it
not to introduce codec issues if I use it as a billing target.

Any help or insight would be greatly appreciated.

Thanks,

--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : +1-678-954-0670
Direct : +1-678-954-0671

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users