please update and test trunk
1) I changed the core to remove the excess data by default in your scenario
2) I added variables you can use to control it origination_callee_id_name origination_callee_id_number which belong in {} in the dial string eg {origination_callee_id_number=1234}openzap/1/a/1234
-----BEGIN PGP SIGNED MESSAGE-----Hi Anthony,
Hash: SHA1
just to make it clear: my goal is to avoid to see something (newly
introduced since 1 or 2 weeks) like "1/a/890327" for outgoing in the
caller's display after answering the call (for openzap calls). I want
simply e.g. "89327". I don't want to put the call into "answer" state
before the called side demands it. So I'm not sure if sip_callee_* is
the right way to follow as long as it needs the answer state.
regards
helmut
iD8DBQFK3Itu4tZeNddg3dwRAvREAKCrZcRM+TnypdVOczpe2+q26b3BYQCfadrY
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
tdA2XIc/hpuIv/916eu4GFo=
=y6Md
-----END PGP SIGNATURE-----
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org