Hello All,
I had bla working with v1.3.0, but it isn't with v1.3.1 .
I didn't expect a maintenance release to require a configuration change, so I am confused. V1.3.1 appears to need a pua_bla server address statement in the modparams. I wasn't using one with v1.3.0, and it appears not to be allowed.
The presence server configuration is very simple, just about straight from the example. It's attached as bla.cfg
I think I have an idea about what's wrong, but not why. Attached also is are ngrep traces of the first and second UAs registering correctly with v1.3.0 and the first UA registering correctly with v1.3.1 . Then an ngrep trace of the second UA registering incorrectly with v1.3.1 . The NOTIFY that should be relayed from the second UA to the first is missing. The attached files are named firstphone-register-130.log, secondphone-register-130.log, firstphone-register-131.log and secondphone-register-131.log .
Any pointers to the problem would be greatly appreciated.
- Jeremy
On Tue, March 18, 2008 5:56 pm, Jeremy George wrote:
I had bla working with v1.3.0, but it isn't with v1.3.1 .
I didn't expect a maintenance release to require a configuration change, so I am confused. V1.3.1 appears to need a pua_bla server address statement in the modparams. I wasn't using one with v1.3.0, and it appears not to be allowed. [..]
Hi Jeremy,
this parameter was introduced in 1.3.1, you're right. It was necessary to keep the server working if you want to use "more proxies", but i'm not sure what this mean. ;-) You'll find the commit in question in revision 3780.
I can't help you with to the problem you face, unfortunately. Perhaps Anca can comment on this.
Cheers,
Henning
Hi Jeremy,
Problems in bla were reported by someone else some time ago. I have worked at it and committed a fix in trunk. Unfortunately, as I waited for a positive reply and was also quite busy I did not manage to do the backport before the 1.3.1 release. I have applied the patch now in 1.3 branch. I am sorry I have to say this, but you should either take the presence, pua and pua_bla modules form the svn branch 1.3 or apply the patches.
Regards, Anca Vamanu
Jeremy George wrote:
Hello All,
I had bla working with v1.3.0, but it isn't with v1.3.1 .
I didn't expect a maintenance release to require a configuration change, so I am confused. V1.3.1 appears to need a pua_bla server address statement in the modparams. I wasn't using one with v1.3.0, and it appears not to be allowed.
The presence server configuration is very simple, just about straight from the example. It's attached as bla.cfg
I think I have an idea about what's wrong, but not why. Attached also is are ngrep traces of the first and second UAs registering correctly with v1.3.0 and the first UA registering correctly with v1.3.1 . Then an ngrep trace of the second UA registering incorrectly with v1.3.1 . The NOTIFY that should be relayed from the second UA to the first is missing. The attached files are named firstphone-register-130.log, secondphone-register-130.log, firstphone-register-131.log and secondphone-register-131.log .
Any pointers to the problem would be greatly appreciated.
- Jeremy
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
-
Anca Vamanu -
Henning Westerholt -
Jeremy George