Hello All.
I have an ATA from a company called WorldAccxx and I'm trying to get it working with ser. ser is serving multiple domains right now. My question is this;
This particular ATA never sends <user>@domain.com when registering. Instead it always seems to send <user>@11.11.11.11 so is there a way to associate this ATA with a particular served domain?
Also, can anyone tell me if this ATA seems to be RFC3261 compliant? It seems to me that if I configure the ATA to use a SIP proxy of sip.mycompany.com and it sends the REGISTER message as <user>@some.ip.address then something is wrong.
Regards, Paul
_______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
Java Rockx wrote:
Hello All.
I have an ATA from a company called WorldAccxx and I'm trying to get it working with ser. ser is serving multiple domains right now. My question is this;
This particular ATA never sends <user>@domain.com when registering. Instead it always seems to send <user>@11.11.11.11 so is there a way to associate this ATA with a particular served domain?
do: if (uri=~"[@:]11.11.11.11") rewritehost("defaultdomain.com");
bogdan
<> Also, can anyone tell me if this ATA seems to be RFC3261 compliant? It seems to me that if I configure the ATA to use a SIP proxy of sip.mycompany.com and it sends the REGISTER message as <user>@some.ip.address then something is wrong.
Regards, Paul
Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Bogdan-Andrei IANCU wrote:
Java Rockx wrote:
Hello All.
I have an ATA from a company called WorldAccxx and I'm trying to get it working with ser. ser is serving multiple domains right now. My question is this;
This particular ATA never sends <user>@domain.com when registering. Instead it always seems to send <user>@11.11.11.11 so is there a way to associate this ATA with a particular served domain?
do: if (uri=~"[@:]11.11.11.11") rewritehost("defaultdomain.com");
bogdan
<> Also, can anyone tell me if this ATA seems to be RFC3261 compliant? It seems to me that if I configure the ATA to use a SIP proxy of sip.mycompany.com and it sends the REGISTER message as <user>@some.ip.address then something is wrong.
Check the version of software. With version 3.1 (I believe) you need to set one of the bit mask flag fields to a specific value in order to use SRV records. You may even have to set a particular value if you want v1 or v2 style records. In any case my version 2.16 ATA support _sip._udp.myproxy.com just fine.
Regards, Paul
Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Steve Blair writes:
You may even have to set a particular value if you want v1 or v2 style records. In any case my version 2.16 ATA support _sip._udp.myproxy.com just fine.
speaking of ata, i recently noticed that it doesn't handle refer requests correctly. if it gets refer to sip:foo@bar.com, it replaces bar.com with its own domain in the invite that it generates from the refer. does anyone have any cure for that?
-- juha
At 06:06 PM 10/15/2004, Juha Heinanen wrote:
Steve Blair writes:
You may even have to set a particular value if you want v1 or v2 style records. In any case my version 2.16 ATA support _sip._udp.myproxy.com just fine.
speaking of ata, i recently noticed that it doesn't handle refer requests correctly. if it gets refer to sip:foo@bar.com, it replaces bar.com with its own domain in the invite that it generates from the refer. does anyone have any cure for that?
it depends. We use REFER for click-to-dial in which we define the target URI. In this scenario we define it in a way that includes the target domain in userpart of URI and SER uses then subst_uri to expand it to the right place. However, that does not work if the target URI can be created by anybody.
-jiri
Jiri Kuthan writes:
it depends. We use REFER for click-to-dial in which we define the target URI. In this scenario we define it in a way that includes the target domain in userpart of URI and SER uses then subst_uri to expand it to the right place. However, that does not work if the target URI can be created by anybody.
thanks for the info regarding your hack. i would rather see cisco to fix their code or if they don't do it, fortunately there are good alternatives to ata.
how about cisco gw? it looks to me that it can't handle refer correctly either. when it receives a refer where refer-to has some foreign domain, it still starts to go though its destination pattern list where only the user part is compared.
-- juha
I have a case open with cisco for this problem for 5 months. It took forever to convince him that this is not the right implementation. It should send an INVITE from the REFER message. But he still didn't care to open a bug case with design engineer...
how about cisco gw? it looks to me that it can't handle refer correctly either. when it receives a refer where refer-to has some foreign domain, it still starts to go though its destination pattern list where only the user part is compared.
-- juha
-
Bogdan-Andrei IANCU -
Java Rockx -
Jiri Kuthan -
Juha Heinanen -
Richard -
Steve Blair