Hi Anca,
Thanks for the quick reply. I wondered a little about the phones, too. Alan sent me a note privately, very tactfully reminding me that I'd sent less phone information than I should have.
The Polycom 650: bootrom.ld version: 3.2.3.0002 sip version: 2.1.2.0078
The Polycom 330: bootrom.lod verion: 3.2.3.0021 sip version: 2.1.2.0049
Both phone.cfgs are attached, as well ngrep traces from reboots. I did two traces, rebooting each phone separately.
Again, I appreciate the help very much. Thanks.
- Jeremy
-----Original Message----- From: Anca-Maria Vamanu [mailto:anca@voice-system.ro] Sent: Thursday, July 12, 2007 08:18 AM To: 'Jeremy George' Cc: users@openser.org Subject: Re: [OpenSER-Users] BLA errors
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
Hi Jeremy,
There seems to be a problem with the phones configuration. The third party should be set to the BLA AOR(the address of the shared line).
In the trace, the problem is with this Subscribe which never reaches the presence-bla server because it gets looped. The correct Subscribe should have the BLA AOR at the R-URI and in TO header and the phones address in FROM header.
U 75.56.10.117:5060 -> 128.91.3.19:5060 SUBSCRIBE sip:helen@128.91.3.19:5060 SIP/2.0..Via: SIP/2.0/UDP 75.56.10.117 ;branch=z9hG4bK7f0a19cB285D501..From: "Helen" sip:helen@128.91.3.19;tag=C 4C66DB5-246677AA..To: sip:helen@128.91.3.19:5060..CSeq: 1 SUBSCRIBE..Call -ID: 12eefb6-828276bb-91d03f10@75.56.10.117..Contact: <sip:helen@75.56.10.1 17>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NO TIFY, PRACK, UPDATE, REFER..Event: call-info..User-Agent: PolycomSoundPoint IP-SPIP_330-UA/2.1.2.0049..Max-Forwards: 70..Expires: 1800..Content-Length:
0.... # U 128.91.3.19:5060 -> 75.56.10.117:5060 SUBSCRIBE sip:helen@75.56.10.117 SIP/2.0..Record-Route: <sip:128.91.3.19;lr =on;ftag=C4C66DB5-246677AA>..Via: SIP/2.0/UDP 128.91.3.19;branch=z9hG4bKe65 c.50632aa3.0..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bK7f0a19cB285D501.. From: "Helen" sip:helen@128.91.3.19;tag=C4C66DB5-246677AA..To: <sip:helen @128.91.3.19:5060>..CSeq: 1 SUBSCRIBE..Call-ID: 12eefb6-828276bb-91d03f10@7 5.56.10.117..Contact: sip:helen@75.56.10.117..Allow: INVITE, ACK, BYE, CA NCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..Even t: call-info..User-Agent: PolycomSoundPointIP-SPIP_330-UA/2.1.2.0049..Max-F orwards: 70..Expires: 1800..Content-Length: 0.... # U 75.56.10.117:5060 -> 128.91.3.19:5060 SIP/2.0 482 Loop Detected..Via: SIP/2.0/UDP 128.91.3.19;branch=z9hG4bKe65c. 50632aa3.0..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bK7f0a19cB285D501..Fr om: "Helen" sip:helen@128.91.3.19;tag=C4C66DB5-246677AA..To: <sip:helen@1 28.91.3.19:5060>..CSeq: 1 SUBSCRIBE..Call-ID: 12eefb6-828276bb-91d03f10@75. 56.10.117..Contact: sip:helen@75.56.10.117..Record-Route: <sip:128.91.3.1 9;lr=on;ftag=C4C66DB5-246677AA>..Event: call-info..User-Agent: PolycomSound PointIP-SPIP_330-UA/2.1.2.0049..Content-Length: 0....
regards,
Anca
Jeremy George wrote:
Hi Anca,
Thanks for the quick reply. I wondered a little about the phones, too. Alan sent me a note privately, very tactfully reminding me that I'd sent less phone information than I should have.
The Polycom 650: bootrom.ld version: 3.2.3.0002 sip version: 2.1.2.0078
The Polycom 330: bootrom.lod verion: 3.2.3.0021 sip version: 2.1.2.0049
Both phone.cfgs are attached, as well ngrep traces from reboots. I did two traces, rebooting each phone separately.
Again, I appreciate the help very much. Thanks.
- Jeremy
Thanks, Anca. The configuration is corrected and the SUBSCRIBE r-uri, to and from are as you said. An ngrep is attached.
In no fork mode on the bla server I get this:
0(16982) ERROR: parse_uri: bad char '@' in state 5 parsed: sip:helen@128.91.3.19 (21) / sip:helen@128.91.3.19@75.56.10.117 (34) 0(16982) ERROR: uri2proxy: bad_uri: sip:helen@128.91.3.19@75.56.10.117 0(16982) ERROR: uri2sock: Can't create a dst proxy 0(16982) PRESENCE:notify: ERROR in function tmb.t_request_within 0(16982) PRESENCE: publ_notify: Could not send notify fordialog;sla 0(16982) PRESENCE:update_presentity: ERROR while sending notify 0(16982) PRESENCE:handle_publish: ERROR occured while updating presentity 0(16982) PRESENCE: handle_publish: ERROR occured 0(16982) ERROR:forward_reply: no 2nd via found in reply 0(16982) ERROR:forward_reply: no 2nd via found in reply 0(16982) ERROR:forward_reply: no 2nd via found in reply 0(16982) ERROR:forward_reply: no 2nd via found in reply 0(16982) ERROR:forward_reply: no 2nd via found in reply
And entries in the pua table seem to just to grow until I have to delete them manually.
Thanks, again.
- Jeremy
-----Original Message----- From: Anca-Maria Vamanu [mailto:anca@voice-system.ro] Sent: Thursday, July 12, 2007 10:38 AM To: Jeremy George Cc: users@openser.org Subject: Re: [OpenSER-Users] BLA errors
Hi Jeremy,
There seems to be a problem with the phones configuration. The third party should be set to the BLA AOR(the address of the shared line).
In the trace, the problem is with this Subscribe which never reaches the presence-bla server because it gets looped. The correct Subscribe should have the BLA AOR at the R-URI and in TO header and the phones address in FROM header.
U 75.56.10.117:5060 -> 128.91.3.19:5060 SUBSCRIBE sip:helen@128.91.3.19:5060 SIP/2.0..Via: SIP/2.0/UDP 75.56.10.117 ;branch=z9hG4bK7f0a19cB285D501..From: "Helen" sip:helen@128.91.3.19;tag=C 4C66DB5-246677AA..To: sip:helen@128.91.3.19:5060..CSeq: 1 SUBSCRIBE..Call -ID: 12eefb6-828276bb-91d03f10@75.56.10.117..Contact: <sip:helen@75.56.10.1 17>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NO TIFY, PRACK, UPDATE, REFER..Event: call-info..User-Agent: PolycomSoundPoint IP-SPIP_330-UA/2.1.2.0049..Max-Forwards: 70..Expires: 1800..Content-Length:
-
Anca-Maria Vamanu -
Jeremy George