12 Jul
2007
12 Jul
'07
3:18 p.m.
Hello,
The implementation of the bla extension has been done according to the
specifications in draft-anil-sipping-bla-03.txt, and tested with
Polycom 430.
Since we received positive feedback from users impementing BLA, I am
thinking that the phones you use have a different behaviour and that
here is the cause of the errors.
To detect the exact cause I would need some more data. Could you send
me a part of the log , after starting openser and the first phones
registers, subscribes and is sent a Notify?
regards,
Anca Vamanu
Jeremy George wrote:
Hello All,
I have BLA implemented, with errors. An ngrep trace of relevant packets
showing errors follows. The configurations of both main proxy and bla
presence server are attached.
I stripped the main proxy to the bone. No outside routing at all. The
bla presence server is almost all from the sample.
75.56.10.115 is a Cisco 7960 with one line registered: jeremy/private
75.56.10.116 is a Polycom 650 with two lines registered: jessica/private
and helen/shared
75.56.10.117 is a Polycom 330 with two lines registered: didama/private
and helen/shared
128.91.3.19 is the main proxy running openser v1.2.1 .
128.91.2.215 is the bla presence server running openser svn 2413 .
This error: "1(1184) PUA:subs_cback_func: no reply message found" is
being produced repeatedly on the bla presence server.
Finally, I'm getting these error messages on the bla presence server:
0(1284) PUA_BLA: handle_notify: ERROR Notify in a non existing dialog
0(1284) WARNING: script writer didn't release transaction
From time-to-time pua entries eat all of available memory. Curiously,
they were all for the Polycom 330 and none were for the Polycom 650.
Any help is greatly appreciated. Thanks.
- Jeremy