Hi! My sip phone has troubles to understand which sip address to contact when it receives a redirection from my openser: In fact 'To' header field contains the new uri and the last one... So now I try to remove the last one from the field but I don't know how to do this!
Can somebody help me?
Thank you!
Michel
On 09/11/06 11:04, Michel Zenone wrote:
Hi! My sip phone has troubles to understand which sip address to contact when it receives a redirection from my openser: In fact 'To' header field contains the new uri and the last one... So now I try to remove the last one from the field but I don't know how to do this!
Can somebody help me?
The phone is quite broken if it adds two To headers or a malformed To headers. You should ask the vendor for a fix rather than trying to patch it on call path. You will get other troubles.
Cheers, Daniel
Thank you!
Michel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
But it's my openser that puts two To headers :-) ! Have you an idea to make openser define the new uri (I use exec_dset) removing the last one?
Regards,
Michel
On Mon, 2006-09-11 at 11:16 +0300, Daniel-Constantin Mierla wrote:
On 09/11/06 11:04, Michel Zenone wrote:
Hi! My sip phone has troubles to understand which sip address to contact when it receives a redirection from my openser: In fact 'To' header field contains the new uri and the last one... So now I try to remove the last one from the field but I don't know how to do this!
Can somebody help me?
The phone is quite broken if it adds two To headers or a malformed To headers. You should ask the vendor for a fix rather than trying to patch it on call path. You will get other troubles.
Cheers, Daniel
Thank you!
Michel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
On 09/11/06 11:44, Michel Zenone wrote:
But it's my openser that puts two To headers :-) ! Have you an idea to make openser define the new uri (I use exec_dset) removing the last one?
then you have a mistake on your config. OpenSER does not add To header by default. Check if you have deleted the old one.
Anyhow, changing the To header is not recommended inside a SIP proxy, it will break the transaction/dialog matching if you do not do the backward translation for replies.
Daniel
Regards,
Michel
On Mon, 2006-09-11 at 11:16 +0300, Daniel-Constantin Mierla wrote:
On 09/11/06 11:04, Michel Zenone wrote:
Hi! My sip phone has troubles to understand which sip address to contact when it receives a redirection from my openser: In fact 'To' header field contains the new uri and the last one... So now I try to remove the last one from the field but I don't know how to do this!
Can somebody help me?
The phone is quite broken if it adds two To headers or a malformed To headers. You should ask the vendor for a fix rather than trying to patch it on call path. You will get other troubles.
Cheers, Daniel
Thank you!
Michel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
In fact my openser does this when it acts as a redirection server... It changes the To header field and does an 'sl_send_reply("300", "Redirect")'. For example, with Xlite it works fine.
Have I bad written my code? If yes, what could it be?
Regards,
Michel
On Mon, 2006-09-11 at 12:43 +0300, Daniel-Constantin Mierla wrote:
On 09/11/06 11:44, Michel Zenone wrote:
But it's my openser that puts two To headers :-) ! Have you an idea to make openser define the new uri (I use exec_dset) removing the last one?
then you have a mistake on your config. OpenSER does not add To header by default. Check if you have deleted the old one.
Anyhow, changing the To header is not recommended inside a SIP proxy, it will break the transaction/dialog matching if you do not do the backward translation for replies.
Daniel
Regards,
Michel
On Mon, 2006-09-11 at 11:16 +0300, Daniel-Constantin Mierla wrote:
On 09/11/06 11:04, Michel Zenone wrote:
Hi! My sip phone has troubles to understand which sip address to contact when it receives a redirection from my openser: In fact 'To' header field contains the new uri and the last one... So now I try to remove the last one from the field but I don't know how to do this!
Can somebody help me?
The phone is quite broken if it adds two To headers or a malformed To headers. You should ask the vendor for a fix rather than trying to patch it on call path. You will get other troubles.
Cheers, Daniel
Thank you!
Michel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Could you post the network trace and configuration snippet which you added for redirect handling?
Cheers, Daniel
On 09/11/06 12:47, Michel Zenone wrote:
In fact my openser does this when it acts as a redirection server... It changes the To header field and does an 'sl_send_reply("300", "Redirect")'. For example, with Xlite it works fine.
Have I bad written my code? If yes, what could it be?
Regards,
Michel
On Mon, 2006-09-11 at 12:43 +0300, Daniel-Constantin Mierla wrote:
On 09/11/06 11:44, Michel Zenone wrote:
But it's my openser that puts two To headers :-) ! Have you an idea to make openser define the new uri (I use exec_dset) removing the last one?
then you have a mistake on your config. OpenSER does not add To header by default. Check if you have deleted the old one.
Anyhow, changing the To header is not recommended inside a SIP proxy, it will break the transaction/dialog matching if you do not do the backward translation for replies.
Daniel
Regards,
Michel
On Mon, 2006-09-11 at 11:16 +0300, Daniel-Constantin Mierla wrote:
On 09/11/06 11:04, Michel Zenone wrote:
Hi! My sip phone has troubles to understand which sip address to contact when it receives a redirection from my openser: In fact 'To' header field contains the new uri and the last one... So now I try to remove the last one from the field but I don't know how to do this!
Can somebody help me?
The phone is quite broken if it adds two To headers or a malformed To headers. You should ask the vendor for a fix rather than trying to patch it on call path. You will get other troubles.
Cheers, Daniel
Thank you!
Michel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
So here is a part of my openser.cfg:
... exec_dset("NEWURI=$$(/usr/local/openser-1.1.0-tls/uri-folder/uri_def $$SIP_USER $fu);echo $$NEWURI");
exec_msg("echo $$(date)': new uri def: ' $$SIP_RURI 'from '$fu $$SIP_DID|cat >>/root/Memos/openrec_uri.txt");
sl_send_reply("300", "Redirect"); return; ...
And this is a part of '/var/log/messages':
Sep 11 12:05:32 localhost /usr/local/sbin/openser[1674]: ERROR: parse_uri: bad port in uri (error at char @ in state 8) parsed: <sip:testeur@192.168.0.102 sip:352000000>(39) /<sip:testeur@192.168.0.102 sip:352000000@192.168.0.102> (53) Sep 11 12:05:32 localhost /usr/local/sbin/openser[1674]: WARNING: append_var: URI not parsed Sep 11 12:05:39 localhost /usr/local/sbin/openser[1680]: ERROR: exec_msg: cmd echo 'select pn_md1_l1_ring from pn where pn_phonenumber=352000000' |cat >>/root/Memos/openrec_uri.txt failed. exit_status=-1, errno=32: Broken pipe Sep 11 12:05:39 localhost /usr/local/sbin/openser[1677]: ERROR: parse_uri: bad port in uri (error at char t in state 8) parsed: <sip:testeur3@192.168.0.102 sip:>(31) /<sip:testeur3@192.168.0.102 sip:testeur@192.168.0.120:5080> (57) Sep 11 12:05:39 localhost /usr/local/sbin/openser[1677]: WARNING: append_var: URI not parsed
Not very good..!
Regards,
Michel
Returned uri from your script has bad format. The error comes when the module tries to add the result of your script as R-URI. Check you shell script.
If you want to append it to reply and use a database to store that value + openser v1.1.0, then you can use avp_db_query(0 to pull the value from database and avp_pushto() function to push the resutl fo the SQL query in R-RUI. See the readme of avpops module for more.
Cheers, Daniel
On 09/11/06 13:07, Michel Zenone wrote:
So here is a part of my openser.cfg:
... exec_dset("NEWURI=$$(/usr/local/openser-1.1.0-tls/uri-folder/uri_def$$SIP_USER $fu);echo $$NEWURI");
exec_msg("echo $$(date)': new uri def: ' $$SIP_RURI 'from '$fu $$SIP_DID|cat >>/root/Memos/openrec_uri.txt"); sl_send_reply("300", "Redirect"); return; ...And this is a part of '/var/log/messages':
Sep 11 12:05:32 localhost /usr/local/sbin/openser[1674]: ERROR: parse_uri: bad port in uri (error at char @ in state 8) parsed: <sip:testeur@192.168.0.102 sip:352000000>(39) /<sip:testeur@192.168.0.102 sip:352000000@192.168.0.102> (53) Sep 11 12:05:32 localhost /usr/local/sbin/openser[1674]: WARNING: append_var: URI not parsed Sep 11 12:05:39 localhost /usr/local/sbin/openser[1680]: ERROR: exec_msg: cmd echo 'select pn_md1_l1_ring from pn where pn_phonenumber=352000000' |cat >>/root/Memos/openrec_uri.txt failed. exit_status=-1, errno=32: Broken pipe Sep 11 12:05:39 localhost /usr/local/sbin/openser[1677]: ERROR: parse_uri: bad port in uri (error at char t in state 8) parsed: <sip:testeur3@192.168.0.102 sip:>(31) /<sip:testeur3@192.168.0.102 sip:testeur@192.168.0.120:5080> (57) Sep 11 12:05:39 localhost /usr/local/sbin/openser[1677]: WARNING: append_var: URI not parsed
Not very good..!
Regards,
Michel
Ok, thanks! I will probably try in this way! So, I must suppose that 'exec_dset' only adds a new Sip address to the 'To' header field without removing the last one?
Regards,
Michel
On Mon, 2006-09-11 at 13:17 +0300, Daniel-Constantin Mierla wrote:
Returned uri from your script has bad format. The error comes when the module tries to add the result of your script as R-URI. Check you shell script.
If you want to append it to reply and use a database to store that value
- openser v1.1.0, then you can use avp_db_query(0 to pull the value from
database and avp_pushto() function to push the resutl fo the SQL query in R-RUI. See the readme of avpops module for more.
Cheers, Daniel
On 09/11/06 13:07, Michel Zenone wrote:
So here is a part of my openser.cfg:
... exec_dset("NEWURI=$$(/usr/local/openser-1.1.0-tls/uri-folder/uri_def$$SIP_USER $fu);echo $$NEWURI");
exec_msg("echo $$(date)': new uri def: ' $$SIP_RURI 'from '$fu $$SIP_DID|cat >>/root/Memos/openrec_uri.txt"); sl_send_reply("300", "Redirect"); return; ...And this is a part of '/var/log/messages':
Sep 11 12:05:32 localhost /usr/local/sbin/openser[1674]: ERROR: parse_uri: bad port in uri (error at char @ in state 8) parsed: <sip:testeur@192.168.0.102 sip:352000000>(39) /<sip:testeur@192.168.0.102 sip:352000000@192.168.0.102> (53) Sep 11 12:05:32 localhost /usr/local/sbin/openser[1674]: WARNING: append_var: URI not parsed Sep 11 12:05:39 localhost /usr/local/sbin/openser[1680]: ERROR: exec_msg: cmd echo 'select pn_md1_l1_ring from pn where pn_phonenumber=352000000' |cat >>/root/Memos/openrec_uri.txt failed. exit_status=-1, errno=32: Broken pipe Sep 11 12:05:39 localhost /usr/local/sbin/openser[1677]: ERROR: parse_uri: bad port in uri (error at char t in state 8) parsed: <sip:testeur3@192.168.0.102 sip:>(31) /<sip:testeur3@192.168.0.102 sip:testeur@192.168.0.120:5080> (57) Sep 11 12:05:39 localhost /usr/local/sbin/openser[1677]: WARNING: append_var: URI not parsed
Not very good..!
Regards,
Michel
-
Daniel-Constantin Mierla -
Michel Zenone