So this seems to be a monologue ;-)


Patton sends SIP Info message with advice of charge information that belong
to the dialog of the call (call-id etc. match the call).



08:12:03  SIP_TR> [STACK] > Stack: to 10.99.10.2

INFO sip:[email protected]:5060;line=6x8d6uul;x-sipX-nonat SIP/2.0

Via: SIP/2.0/UDP 10.99.20.6:5060;branch=z9hG4bK2a7950b4d75d5bf76

Route: <sip:10.99.10.2:5060
;lr;sipXecs-CallDest=LD;sipXecs-rs=*auth~.*from~ZjU4NWx5cXVqYg$60$60!dfc2e14fbd8040972c2f37b0e612a9d5>

Max-Forwards: 70

From: <sip:[email protected];user=phone>;tag=2706171110

To: "Jan Thiemo Fricke" <sip:[email protected]>;tag=f585lyqujb

Call-ID: 3c87f581a2b3-nxoxs65f8ut0

CSeq: 18895 INFO

User-Agent: Patton SN4960 1E30V 00A0BA05C50E R5.6 2010-09-10 H323 RBS SIP
M5T SIP Stack/4.0.29.29

Content-Type: application/QSIG

Content-Length: 44



91a112020100020122300aa1053003020101820100





I could help to decode the hex formatted isdn information to make them
useful. Could this information be used by a SipX Proxy Plugin to enrich the
cdrs with actual costs of external calls? As I’m not familiar with the
development of proxy plugins it would be much effort for me. But maybe this
not so hard if you know how these things work.



Regards



Jan





*Von:* Jan Fricke [mailto:[email protected]]
*Gesendet:* Donnerstag, 12. Januar 2012 18:11
*An:* sipXecs developer discussions
*Betreff:* Re: Discussion about Advice of Charge Information



Ok looking for some further information I found out that patton after all
supports aoc also from isdn to sip. I did not test it yet but the admin
manuals says:
"AOC Over SIP (Optional)
This enhancement sends AOC information transparently from ISDN (or H.323)
to SIP and vice versa. AOCD
elements are hex-encoded and sent as application/QSIG content in SIP INFO
messages during a session."

Has anybody tested that yet? At the first glance it doesn't seem to be
compliant to any standard or draft. Are there any except the 3GPP document
that I posted? Are there any plans to support such charging methods?

2012/1/12 Jan Fricke <[email protected]>

Hi members,

lately we have talked with a customer about billing in sipxecs. Some people
see a lack of function at the billing part in sipx. Cdrs contain the caller
and the callee and the duration of the call but not the costs.

ISDN providers transfer AOC information in facility messages. Are there any
gateways that support the translation from isdn to SIP? As far as I know
Patton Gateways only transfer AOC from isdn to isdn and from isdn to H.323.
How about Audiocodes? Are there VoIP Providers that use some standard to
transfer AOC information?



Information about AOC in VoIP seem to be rare. Asterisk based systems with
interface cards have less problems because they can transfer these
information local. Snom seems to transfer the AOC information with SIP INFO
messages in the xml body (defined by a 3GPP NGN Standard TS 24.647 V8.3.0
http://www.quintillion.co.jp/3GPP/Specs/24647-830.pdf) from their PBX
SnomOne to the Snom phones.



Has anybody already dealed with these stuff?



Regards



Jan



_____________________________

Jan Fricke B.Sc. Cs.



IANT- APPLIED NGN-TECHNOLOGIES



Schlüsselfertige VoIP-Lösungen und mehr...



Member of GROUPLINK



IANT GmbH

Salzdahlumer Straße 46/48

D-38302 Wolfenbüttel

Fon: +49/(0)5331/ 900989-0

Fax: +49/(0)5331/ 900989-499



Mail: [email protected]

Internet: www.iant.de





Bankverbindung: IANT GmbH, Konto-Nr. 12 95 98 50 00, Volksbank BraWo  (BLZ 269
910 66); IBAN-Nr.: DE02 2699 1066 1295 9850 00, BIC: GENODEF1WOB;
Steuer-Nr.: 51/DP2013; Ust.-IdNr: DE264352710; HRB 201710, Amtsgericht
Braunschweig; Geschäftsführer: Dipl.-Ing. Jan Schumacher, Prof. Dr.-Ing.
Diederich Wermser



Diese E-Mail kann vertrauliche und/oder rechtlich geschützte Informationen
enthalten. Wenn Sie nicht der richtige Empfänger sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail.

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient or have received this e-mail in error please
notify the sender immediately and delete this e-mail.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to