Hi,
I have a registered Linksys, behind a USR 9108 modem. I can detect its nat, call Linksys and speak normally, but when I try to make a call from Linksys, call breaks down right after call setup. Linksys sends the via and contact ip's as 0.0.0.0 in invite messages and fix_nated_contact does not work. This is possibly because of the modem but, there are no extra configurations that can cause this in the modem. I will be glad if you can direct me with your experiences. thank you... _________________________________________________________________ Live.com'u deneyin: çevrimiçi dünyanýzý bir araya getirin; haberler, spor, hava durumu ve çok daha fazlasý. http://www.live.com/getstarted
Hello users,
i know the subject is ugly but i am dealing with a nasty registrar.
Here is the architecture :
UAC <--> openser <--> registrar (not openser)
Because of various reasons, i HAVE to make openser do save("location") and this has to be done only when registrar replies a 200 OK.
Here is a piece of my openser.conf :
------------ route{ if (method))"REGISTER") { t_on_reply("1"); t_relay("udp:registrar") }; }
route[1] { save_noreply("location"); }
onreply_route[1] { if (status=="200") { route(1); }; } ------------
My problem is, when a 200 OK arrives, User-Agent and Allow header field disappeared.
As far as i understood the source code of 'save' function, it reads the original message (in my case, the received 200 OK packet) before recording the contact. This was confirmed when i tried to append_hf("User-Agent: xxx\r\n") before saving -> it was null in the database.
Do you have any idea how i could get back these fields when receiving a 200 OK?
Best regards,
Hi,
unfortunately I think it is not possible to do what you want. save() function is specifically ddesigned to work on a SIP request and not on a SIP reply.
regards, bogdan
Jean-Michel Foucher wrote:
Hello users,
i know the subject is ugly but i am dealing with a nasty registrar.
Here is the architecture :
UAC <--> openser <--> registrar (not openser)
Because of various reasons, i HAVE to make openser do save("location") and this has to be done only when registrar replies a 200 OK.
Here is a piece of my openser.conf :
route{ if (method))"REGISTER") { t_on_reply("1"); t_relay("udp:registrar") }; }
route[1] { save_noreply("location"); }
onreply_route[1] { if (status=="200") { route(1); }; }
My problem is, when a 200 OK arrives, User-Agent and Allow header field disappeared.
As far as i understood the source code of 'save' function, it reads the original message (in my case, the received 200 OK packet) before recording the contact. This was confirmed when i tried to append_hf("User-Agent: xxx\r\n") before saving -> it was null in the database.
Do you have any idea how i could get back these fields when receiving a 200 OK?
Best regards,
Bogdan,
unfortunately I think it is not possible to do what you want. save() function is specifically ddesigned to work on a SIP request and not on a SIP reply.
all right, thank you for your answer.
I'll try to figure sthg out. I will post it if it works in case someone is interested.
Regards,
Hi Jean-Michel,
It looks like Maxim has committed an enhancement to SER to allow save of contacts in on_reply route, but I don't think that addresses your specific issue.
You can check it out here: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/r... http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/s...
Regards, Ovidiu Sas
On 5/9/07, Jean-Michel Foucher jean-michel.foucher@wengo.com wrote:
Bogdan,
unfortunately I think it is not possible to do what you want. save() function is specifically ddesigned to work on a SIP request and not on a SIP reply.
all right, thank you for your answer.
I'll try to figure sthg out. I will post it if it works in case someone is interested.
Regards,
-- cdt,
Jean-Michel Foucher OpenWengo, the free and multiplatform VoIP client http://dev.openwengo.org/
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello,
It looks like Maxim has committed an enhancement to SER to allow save of contacts in on_reply route, but I don't think that addresses your specific issue.
no, unfortunately it does not. Event though save_noreply would be called when a 200 OK is received, save_noreply should use the original REGISTER in order to gather contact information.
You can check it out here: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/r...
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/s...
thanks for the links ;)
best regards,
What about copying the contact in the REGISTER into an AVP. Then we would need a function which stores AVP into location table - e.g. save($avp(s:contacts));
This function should be useable in request and reply route.
regards klaus
Jean-Michel Foucher wrote:
Hello,
It looks like Maxim has committed an enhancement to SER to allow save of contacts in on_reply route, but I don't think that addresses your specific issue.
no, unfortunately it does not. Event though save_noreply would be called when a 200 OK is received, save_noreply should use the original REGISTER in order to gather contact information.
You can check it out here: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/r...
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/s...
thanks for the links ;)
best regards,
On 05/30/07 14:32, Klaus Darilion wrote:
What about copying the contact in the REGISTER into an AVP. Then we would need a function which stores AVP into location table - e.g. save($avp(s:contacts));
This function should be useable in request and reply route.
there is also the expires that should be taken in consideration. Also, in reply, the server can add all the registered contacts, with the afferent expiration times. What is also important, for nat traversal, are the received ip and port, source ip and port, which must be taken from request.
Cheers, Daniel
regards klaus
Jean-Michel Foucher wrote:
Hello,
It looks like Maxim has committed an enhancement to SER to allow save of contacts in on_reply route, but I don't think that addresses your specific issue.
no, unfortunately it does not. Event though save_noreply would be called when a 200 OK is received, save_noreply should use the original REGISTER in order to gather contact information.
You can check it out here: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/r...
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/s...
thanks for the links ;)
best regards,
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Daniel-Constantin Mierla wrote:
On 05/30/07 14:32, Klaus Darilion wrote:
What about copying the contact in the REGISTER into an AVP. Then we would need a function which stores AVP into location table - e.g. save($avp(s:contacts));
This function should be useable in request and reply route.
there is also the expires that should be taken in consideration. Also, in reply, the server can add all the registered contacts, with the afferent expiration times. What is also important, for nat traversal, are the received ip and port, source ip and port, which must be taken from request.
Yes, thats right. My idea was to store all the relevant data into AVP during request processing and reuse the AVPs when storing in reply route (only check if response code is 200)
regards klaus
Cheers, Daniel
regards klaus
Jean-Michel Foucher wrote:
Hello,
It looks like Maxim has committed an enhancement to SER to allow save of contacts in on_reply route, but I don't think that addresses your specific issue.
no, unfortunately it does not. Event though save_noreply would be called when a 200 OK is received, save_noreply should use the original REGISTER in order to gather contact information.
You can check it out here: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/r...
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/registrar/s...
thanks for the links ;)
best regards,
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users