Re: [OpenSIPS-Users] set_advertised_address suspected bug 1.9

Hi, Terrance! No, you cannot change the advertised address in the onreply_route, since the Route headers have already been sent to your UAS. The proper way to do this is to make all the interface changes in the request route. Best regards, Răzvan Crainea OpenSIPS Solutions

Re: [OpenSIPS-Users] opensips 1.9 error (I know it's very generic)

Thx for the reply, but what is the function of rtpproxy? I use asterisk to handle my rtp (media). So can I remove the module from opensip being loaded? Also network congestion, but is on the localhost which is itself, how can there be network congestion? Thx. -- View this message in

Re: [OpenSIPS-Users] set_advertised_address suspected bug 1.9

Hello Razvan, Thank you for your response. The problem I am experiencing is that I cannot catch the 200OK that OpenSIPS sends out except for within the onreply_route. I put debug messages all over the script, and the only place the 200OK that opensips would fire was in the onreply. Can you please

[OpenSIPS-Users] Opensips 1.11 on Centos 6.6, running but not listening?

I am currently running Opensips 1.9 on Debian Whizzy, but as stated on my other thread, I am getting some weird error which opensips would suddenly stop working. So, I am starting a new installation of Opensips 1.11 on Centos 6.6 using the yum install method: 1. I was able to install yum

[OpenSIPS-Users] DROUTING module changing Carrier IDs

I am using OpenSIPS 1.11 and I am recently getting some weird behavior from the DROUTING module. The module is corrupting the Carrier ID that is being returned via AVP. This behavior is occurring only with the Carrier ID, not the gateway or rule IDs, and only when it is returned from the