version 3.11.5-013249 sipXproxy drops Display Name when forwarding.

Hello

I have to do a test for AT&T where the Display Name set on the phone
is forwarded with the outbound Invite to the ITSP. However, I notice
that sipXproxy seems to drop the display name when forwarding.
Attached is a merged and filtered trace (I filtered the relevant
sections using sipx-trace ).

Notice that in Frame 17 the INVITE has the display name "user six" in
the From header. However notice that in Frame 19, the display name is
dropped.  Not sure if I should I be setting the display name
elsewhere. If this is a possible bug, I can file a report.

Thank you for your attention,

Ranga

--

-- 
M. Ranganathan

Hello

I have to do a test for AT&T where the Display Name set on the phone
is forwarded with the outbound Invite to the ITSP. However, I notice
that sipXproxy seems to drop the display name when forwarding.
Attached is a merged and filtered trace (I filtered the relevant
sections using sipx-trace ).

Java compatibility problem

I'd like to get Java compatibility straightened out.

The currently built RPMs have a 'require' for Java version >= 1.6.  The
currently distributed RPM set contains such a Java RPM.

However, this could force a Java upgrade on some users, as earlier
versions of sipX only require Java version >= 1.5.

I looked at the discussions of this issue on sipx-dev.  The last thread
I found starts at
http://list.sipfoundry.org/archive/sipx-dev/msg12614.html  One or two
people suggested we push users to upgrade to Java 1.6.  Damien noted
that we previously stated on sipx-dev
(http://article.gmane.org/gmane.comp.voip.sipx.devel/9437) that there
would be one more version ("3.12", now called 4.0) that would be
compatible with 1.5.  There seemed to be no compelling reasons not to
follow this path, and that pretty much ended the discussion.

So we are now in a state where the code is not compatible with the
discussions on sipx-dev.  I'd like to get this conflict resolved.

Opinions?

Dale

2008-08-19 Need immediate help with VXML. Will pay.

<div>

<div class="Section1">

<p class="MsoNormal"><span>I am looking for some assistance with a VXML that I&rsquo;m
working on. I am willing to pay for your time. Please email me ASAP.<p></p></span></p>

<p class="MsoNormal"><span>I am working with sipXecs open source 3.10.1 and looking for
help with &lt;transfer&gt;, &lt;record&gt;, and Dial Plans.<p></p></span></p>

<p class="MsoNormal"><span><p>&nbsp;</p></span></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; Bobbie Stivers</span><p></p></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; Software and Systems Engineer</span><p></p></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; Information Products, Inc.<p></p></span></p>

<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; Email: <a href="mailto:bobbie <at> InformationProductsInc.com">bobbie <at> InformationProductsInc.com</a></span><p></p></p>

<p class="MsoNormal"><span><p>&nbsp;</p></span></p>

</div>

</div>

version 3.11.5-013249 sipxivr startup issue?

Did an update and a build this morning and here's what happened when I
restarted:

sipXpbx:
sipXpbx: sipXpbx configuration problems found:
sipXpbx:
sipXpbx: Check sipxivr
sipXpbx:    ==== /usr/local/sipx/etc/sipxpbx/autoattendants.xml:
sipXpbx:
sipXpbx: Error at file /usr/local/sipx/etc/sipxpbx/autoattendants.xml,
line 71, char 16
sipXpbx:   Message: Element 'schedule' is not valid for content model:
'((holiday,regularhours),afterhours)'
sipXpbx:
Attempting to start despite configuration problems

Any ideas?

Ranga

--

-- 
M. Ranganathan

Getting error while compiling from source

<div><div dir="ltr">Hi,<br><br>While compiling sipx version 3.11.5 from source i am getting following error:<br><br>BUILD FAILED<br>/root/Desktop/sipx/sipx/sipXconfig/ant-targets.xml:146: Compile failed; see the compiler error output for details.<br><br>Total time: 1 second<br>make[5]: *** [all-ant] Error 1<br>make[5]: Leaving directory `/root/Desktop/sipx/sipx/BUILD/sipXconfig/plugins/nortel'<br>make[5]: Entering directory `/root/Desktop/sipx/sipx/BUILD/sipXconfig/plugins'<br>
make[5]: Nothing to be done for `all-am'.<br>make[5]: Leaving directory `/root/Desktop/sipx/sipx/BUILD/sipXconfig/plugins'<br>make[4]: *** [all-recursive] Error 1<br>make[4]: Leaving directory `/root/Desktop/sipx/sipx/BUILD/sipXconfig/plugins'<br>
make[3]: *** [all-recursive] Error 1<br>make[3]: Leaving directory `/root/Desktop/sipx/sipx/BUILD/sipXconfig'<br>make[2]: *** [all] Error 2<br>make[2]: Leaving directory `/root/Desktop/sipx/sipx/BUILD/sipXconfig'<br><br>Regards,<br>Manoj<br>
</div></div>

FreeSWITCH build error

<div>

<p>g++ -w -DMULTIPLICITY -DEMBED_PERL -I/home/sipxbuild/rpmbuild/BUILD/sipx-freeswitch-1.0.1/src/include -I/home/sipxbuild/rpmbuild/BUILD/sipx-freeswitch-1.0.1/libs/libteletone/src -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -D_GNU_SOURCE -DHAVE_CONFIG_H -c -o freeswitch_perl.o freeswitch_perl.cpp<br>
In file included from freeswitch_perl.cpp:2:<br>
freeswitch_perl.h:13:20: error: EXTERN.h: No such file or directory<br>
freeswitch_perl.h:14:18: error: perl.h: No such file or directory<br>
freeswitch_perl.h:24: error: ISO C++ forbids declaration of 'PerlInterpreter' with no type<br>
freeswitch_perl.h:24: error: expected ';' before '*' token<br>
freeswitch_perl.h:25: error: ISO C++ forbids declaration of 'PerlInterpreter' with no type<br>
freeswitch_perl.h:25: error: expected ';' before '*' token<br>
freeswitch_perl.h:28: error: ISO C++ forbids declaration of 'SV' with no type<br>
freeswitch_perl.h:28: error: expected ';' before '*' token<br>
freeswitch_perl.h:40: error: 'SV' has not been declared<br>
freeswitch_perl.h:49: error: 'PerlInterpreter' has not been declared<br>
mod_perl_extra.h:5: error: variable or field 'mod_perl_conjure_event' declared void<br>
mod_perl_extra.h:5: error: 'PerlInterpreter' was not declared in this scope<br>
mod_perl_extra.h:5: error: 'my_perl' was not declared in this scope<br>
mod_perl_extra.h:5: error: expected primary-expression before '*' token<br>
mod_perl_extra.h:5: error: 'event' was not declared in this scope<br>
mod_perl_extra.h:5: error: expected primary-expression before 'const'<br>
mod_perl_extra.h:5: error: initializer expression list treated as compound expression<br>
mod_perl_extra.h:6: error: variable or field 'mod_perl_conjure_stream' declared void<br>
mod_perl_extra.h:6: error: 'PerlInterpreter' was not declared in this scope<br>
mod_perl_extra.h:6: error: 'my_perl' was not declared in this scope<br>
mod_perl_extra.h:6: error: expected primary-expression before '*' token<br>
mod_perl_extra.h:6: error: 'stream' was not declared in this scope<br>
mod_perl_extra.h:6: error: expected primary-expression before 'const'<br>
mod_perl_extra.h:6: error: initializer expression list treated as compound expression<br>
freeswitch_perl.cpp:5: error: 'STRLEN' does not name a type<br>
freeswitch_perl.cpp: In constructor 'PERL::Session::Session()':<br>
freeswitch_perl.cpp:13: error: 'my_perl' was not declared in this scope<br>
freeswitch_perl.cpp: In constructor 'PERL::Session::Session(char*, CoreSession*)':<br>
freeswitch_perl.cpp:18: error: 'my_perl' was not declared in this scope<br>
freeswitch_perl.cpp: In constructor 'PERL::Session::Session(switch_core_session_t*)':<br>
freeswitch_perl.cpp:34: error: 'my_perl' was not declared in this scope<br>
freeswitch_perl.cpp: At global scope:<br>
freeswitch_perl.cpp:73: error: variable or field 'setPERL' declared void<br>
freeswitch_perl.cpp:73: error: 'int PERL::Session::setPERL' is not a static member of 'class PERL::Session'<br>
freeswitch_perl.cpp:73: error: 'PerlInterpreter' was not declared in this scope<br>
freeswitch_perl.cpp:73: error: 'pi' was not declared in this scope<br>
freeswitch_perl.cpp:74: error: expected ',' or ';' before '{' token<br>
make[8]: *** [freeswitch_perl.o] Error 1<br>
make[8]: Leaving directory `/home/sipxbuild/rpmbuild/BUILD/sipx-freeswitch-1.0.1/src/mod/languages/mod_perl'<br>
make[7]: *** [all] Error 1<br>
make[7]: Leaving directory `/home/sipxbuild/rpmbuild/BUILD/sipx-freeswitch-1.0.1/src/mod/languages/mod_perl'<br>
make[6]: *** [languages/mod_perl-all] Error 1<br>
make[6]: Leaving directory `/home/sipxbuild/rpmbuild/BUILD/sipx-freeswitch-1.0.1/src/mod'<br>
make[5]: *** [all-recursive] Error 1<br>
make[5]: Leaving directory `/home/sipxbuild/rpmbuild/BUILD/sipx-freeswitch-1.0.1/src'<br>
make[4]: *** [all-recursive] Error 1<br>
make[4]: Leaving directory `/home/sipxbuild/rpmbuild/BUILD/sipx-freeswitch-1.0.1'<br>
make[3]: *** [all] Error 2<br>
make[3]: Leaving directory `/home/sipxbuild/rpmbuild/BUILD/sipx-freeswitch-1.0.1'<br>
error: Bad exit status from /var/tmp/rpm-tmp.48593 (%build)<br><br><br>
RPM build errors:<br>
&nbsp;&nbsp;&nbsp; Bad exit status from /var/tmp/rpm-tmp.48593 (%build)<br>
make[2]: *** [build-rpms] Error 1<br>
make[2]: Leaving directory `/home/sipxbuild/src/main/lib/freeswitch/build'<br>
make[1]: *** [freeswitch.bld] Error 2<br>
make[1]: Leaving directory `/home/sipxbuild/src/main/lib'<br>
make: *** [freeswitch] Error 2<br>
[sipxbuild <at> build lib]$<br>
</p>

</div>

Polycom unit test clean up

<div>

<p>Hello,
</p>

<p>In the process of removing support of firmware 1.6 for Polycom, I found the following files are not used in the unit tests:</p>

<p>- expected-phone-2.0.cfg.xml

<br>- expected-phone-2.1.2.cfg.xml

<br>- expected-phone-2.2.0.cfg.xml

<br>- expected-phone-2.2.2.cfg.xml
</p>

<p>- expected-sip-2.0.cfg.xml

<br>- expected-sip-2.1.2.cfg.xml

<br>- expected-sip-2.2.0.cfg.xml

<br>- expected-sip-2.2.2.cfg.xml

<br>- expected-sip-3.0.0.cfg.xml
</p>

<p>As for firmware versions beyond 2.0, they all have compatible format, I don't think we need to distinguish the versions anymore, at least at this point. Leaving those unused files only leads to confusion. I am suggesting to remove all those unused test files. Does anyone have objection?</p>

<p>Thanks

<br>Huijun
</p>

</div>

XECS-845 - Emergency call notification

<div>

<p>It has been suggested to me that an alarm could be raised when a call is placed through the Emergency dial plan.&nbsp; This would cause generic alarm handling - an email to a configured (list of?) administrators would be sent and the alarm would be logged, along with whatever parameters we can get at time of invocation.</p>

<p>The issue <a href="http://track.sipfoundry.org/browse/XECS-845">http://track.sipfoundry.org/browse/XECS-845</a> floats a lot of possibilities, which are beyond the scope of this inquiry.&nbsp; I would just like to get opinions on whether it is worth adding an alarm for this case, which could probably be done very quickly (i.e. in this release).&nbsp; Of course, it would not fire if the set routes emergency numbers out directly.</p>

<p>Thanks,

<br>Carolyn
</p>

</div>

Polish translation

Hi,

Current 3.10.2 Polish translation dates back to 3.8 :(

My company is finishing the update along with Polish prompts.

Should  we  just send patches from time to time (where to?) or should
we have publish a separate language pack on sipfoundry?

I'm in favor of a separate language pack for hmm.. marketing reasons ;)

But  the we would either have to remove Polish from main or live with
basic (included) and "extended" (free 2 download) translations.

Pawel,

Polish translation

Hi,

 Current 3.10.2 Polish translation dates back to 3.8 :(

 My company is finishing the update along with Polish prompts.

 Should  we  just send patches from time to time (where to?) or should
 we have publish a separate language pack on sipfoundry?

 I'm in favor of a separate language pack for hmm.. marketing reasons ;)

 But  the we would either have to remove Polish from main or live with
 basic (included) and "extended" (free 2 download) translations.

Pawel,

(no subject)

Witam!

--

-- 
Pozdrowienia,
 ppierscionek <at> urtho.net