VoIP Mailing List Archives

[mcampbellsmith at gmai...]

Hi!

Does freeswitch support extracting the billing data (PortaBilling) in
SIP messages? If so, is there anyway I can get that information to an
extension?

03:36:00.245: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDis­ playMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP sip.mydomain.com:5060;branch=z9hG4­ bK1FF90
From: {sip:61XXXXXXXXX@sip.pennytel.com};­ tag=47E011-580
To: {sip:61XXXXXXXXX@sip.pennytel.com};­
tag=adfde4bc91cd85e752cb0672816ac1­ a6-eb1b
Call-ID: EE04FAB6-F24011DC-803AA58E-D5912FB­ 7
CSeq: 3 REGISTER
PortaBilling: available-funds:7.37 currency:AUD
Contact: {sip:61XXXXXXXXX@sip.mydomain.com:5060};­ expires=3595
Server: Sip EXpress router (0.9.6 (i386/freebsd))
Content-Length: 0

Thanks!

_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[grevenx at me.com]

I'm not sure if you are able to read that header from FS without any
modifications.
What you can try is the generic syntax to get header variables:
{$sip_h_PortaBilling}.
Not sure, but I think this might only work with a set of standard
headers, as well as all non-standard
headers, that really should be prefixed with "X-".

If this does not work, the PortaBilling header should in this case be
renamed to X-PortaBilling, and you would be able
to get it from FreeSWITCH with: {$sip_h_X-PortaBilling}.
That is if it's possible to change that header on the server that
sends it...


Best regards,
Even André

On 17. juni. 2009, at 08.58, Mark Campbell-Smith wrote:

[krice at suspicious.org]

I doubt that header is exposed since its not a standard sip header. However
you could probably patch mod_sofia to expose it without too much trouble...
How difficult that would be is dependant on where in session that comes in

[demuel at thephinix.org]

Porta-Billing from PortaSIP? I've tried their stuff and this is when I saw
the most disgusting piece of scam software on the VoIP world. Their
technical support were the dumbest I ever encountered since time
immemorial....Be very beware, they are just extracting your money but
their services are shit.

[jason at jasonjgw.net]

Ken Rice <krice@suspicious.org> wrote:

[brian at freeswitch.org]

While the header looks valid it should be an X-Header then it would
show up.

/b

On Jun 17, 2009, at 2:32 AM, Ken Rice wrote:

[krice at suspicious.org]

While you are correct Jason, this particular header is not a valid SIP
Header... It should be prefixed with X- ie: "X-Some-Custom-Header: foo"

When you have non-standard headers lib sofia will stick them in a struct on
the backend for us to manually deal with but they are not auto-magically
assigned to channel variables unless they are X- and P- headers (P- headers
are some special meaning headers typically associated with billing and
privacy or are "private" headers