Hi Ping,
I;m glad to here that.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 10.06.2015 08:23, Ping Han wrote:
Hi Bogdan,
I have implemented the new features and they work perfectly.
Thanks,
Chris
On Wed, Jun 10, 2015 at 10:13 AM, Ping Han <[email protected]
<mailto:[email protected]>> wrote:
Thanks, Bogdan,
I have just upgraded Opensips from 1.9 to 2.1 and did not notice
the new features related to uac_auth. I was looking a way to
dynamically match the authentication credentials and I believe the
following new parameters will solve the problem.
auth_realm_avp
auth_username_avp
auth_password_avp
Thanks,
Ping
On Wed, Jun 10, 2015 at 2:01 AM, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Hi Ping,
You should not manually change the cseq in the messages as you
will break the whole dialog (the sequential requests).
The 2.1 version does cseq increasing (with dialog consistency)
when performing uac_auth().
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 05.06.2015 09:39, Ping Han wrote:
Hi Bogdan,
Thanks for your reply.
I am trying to manipulate the CSeq header.
I have attached a packet trace.
In the example 10.216.235.38 sends a SIP Invite to
10.216.235.37 via Opensips. Then 10.216.235.37 challenges
authentication. In the second SIP Invite that contains the
authentication info (frame number 6), I have to increment the
CSeq header otherwise 10.216.235.37 does not like it. The new
CSeq is now set to 2.
If 10.216.235.37 is not able to accept the call, it returns
something other than "200 OK" (606 in this example). Now it
is the problem. Opensips sends back an ACK (frame number 12)
with CSeq set to 1 (not 2). 10.216.235.37 is expecting an ACK
with a CSeq set to 2. The consequence is that 10.216.235.37
keeps sending 606 until times out.
The ACK is internally generated by Opensips and as you said
we can not manipulate it. I am wondering if there is any way
to solve this problem.
PS: 10.216.235.97 is the internal IP of Opensips server and
10.216.235.74 is the external IP.
Thanks,
Ping
On Thu, Jun 4, 2015 at 12:55 AM, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Hi Ping,
There is no access to internally generated ACK and CANCEL
requests.
What are you trying to do ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 03.06.2015 02:53, Ping Han wrote:
Hi,
With Opensips is there a way to manipulate the SIP
headers of a messages that are generated locally by
Opensips. See the example below.
--------------------------------------------
ACK sip:[email protected]:5060
<http://sip:[email protected]:5060> SIP/2.0
Via: SIP/2.0/UDP
192.168.100.74:5060;branch=z9hG4bK5094.3ee05403.1
From:<sip:[email protected]
<mailto:sip%[email protected]>>;tag=1740643510
Call-ID: [email protected]
<mailto:[email protected]>
To:<sip:[email protected]:5060
<http://sip:[email protected]:5060>>;tag=1994410995-1432625097305;
CSeq: 1 ACK
Max-Forwards: 70
User-Agent: OpenSIPS (2.1.0 (x86_64/linux))
Content-Length: 0
--------------------------------------------
Thanks,
Ping Han
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
