[OpenSIPS-Users] Generate Billing-Correlation-ID

Hello. I would to use P-DCS-Billing-Info header with parameters (RFC 5503) for billing purposes. Especially, I need to generate Billing-Correlation-ID. How to implement this in script? Or, I should do this via exec or perl, or other external script? Best regards, Alexander Mustafin mustafin.al

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 1.8.4/1.9.2/1.10.1 Minor Versions

How easy it is to migrate our script from 1.8.x to 1.9.x? Kind Regards, Nick. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] top hiding -- where do I specify my SIP server(s)?

I'm trying to build a very simple instance of top hiding, with a single Asterisk server as my SIP server. Where in OpenSIPS do I put the IP address, or whatever other information might be required, so that OpenSIPS knows to forward packets to / from the Asterisk server? I'm guessing it's in t

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 1.8.4/1.9.2/1.10.1 Minor Versions

Hi, all! Just wanted to let you know that we have just released three new minor versions of OpenSIPS: * OpenSIPS 1.8.4: http://opensips.org/pub/opensips/1.8.4/src/ * OpenSIPS 1.9.2: http://opensips.org/pub/opensips/1.9.2/src/ * OpenSIPS 1.10.1: http://opensips.org/pub/opensips/1.10.1/src/ All

Re: [OpenSIPS-Users] Prevent re-INVITE to T.38

T.38 v2 supports up to 14.4k (V.17), v3 supports 33.6k (V.34). None of my carrier partners' gateways support T.38 v3. A SuperG3 capable fax machine supports up to 33.6k (V.34). Let's say we have two SG3 machines trying to talk to each other with an IP/T.38 v2 link in the middle. Since the gatew

Re: [OpenSIPS-Users] Prevent re-INVITE to T.38

It must be the new fax machines that are using high speeds that are not supported by T.38. Striping SDP completely may create issues ... IIRC you are not allowed to have no SDP in INVITEs. On Mar 12, 2014 8:48 AM, "Jeff Pyle" wrote: > Our use case is a call forward from an inbound carrier gateway

Re: [OpenSIPS-Users] Prevent re-INVITE to T.38

Our use case is a call forward from an inbound carrier gateway to an outbound one. Both do support T.38. In fact, that's the problem. We've seen much higher success rates with fax forwards if both sides stay G.711. Quite interesting considering in many cases both the originating and terminating

Re: [OpenSIPS-Users] Presence: "xmlns" attributes inside element not compliant to RFC3863

Hi, On Mar 11, 2014, at 7:38 PM, Martin Stock wrote: > Hi, > > thanks for your answer. > > >> With OpenSIPS 1.10 the namespace attributes are not defined inside the > >> element. Referring to RFC3863, Section 4.1.1 > >> (https://tools.ietf.org/html/rfc3863#page-5) IMHO this is not intended.