sr-users July 2004

sr-users@lists.kamailio.org

178 participants
449 discussions

RE: [Serusers] Aliasing problem
by Dave Bath 15 Jul '04

15 Jul '04

Perfect. *Bows humbly*. I don't know what possessed me to add that line in - I believe it was when I was trying to work out why adding aliases didn't work. Call me a muppet :-) D -----Original Message----- From: Jan Janak [mailto:jan@iptel.org] Sent: 15 July 2004 08:42 To: Dave Bath Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Aliasing problem Are you calling save("aliases") somewhere in the configuration file ? If so then you should replace it with save("location"), save("aliases") should never be called from the configuration file. Jan. On 15-07 08:40, Dave Bath wrote: > Ok this must be where I am confused... the only alias I have created is > "1000" and is mapped to sip:admin@sip.dev.inmarsat.com > > If I do a "serctl show alias admin" I get what I pasted below... I would > have expected to see the newly created "1000" alias... However, doing a > "serctl show alias 1000" does list admin.. as below > > [root@sip log]# serctl alias show 1000 > <sip:admin@sip.dev.inmarsat.com>;q=1.00;expires=31532649 > <sip:test1@161.30.211.131:5060>;q=0.00;expires=399 > > But it's also showing test1?!?!? WHY! Lol! I have never created any > aliases with test1. Similarly: > > [root@sip dave]# serctl alias show test1 > <sip:admin@<ip1>:5060>;q=0.00;expires=2621 > > Now as far as I know, that last command should have returned nothing, as > I have never created any aliases for test1. > > Also, I know that serweb creates aliases automatically - but it is set > to create numerical aliases. Besides, I am not using serweb to create > users, so that's just something else. > > Are all the registering UAs messing up the aliases somehow? This is > becoming very frustrating! > > Dave > > -----Original Message----- > From: Jan Janak [mailto:jan@iptel.org] > Sent: 15 July 2004 08:31 > To: Dave Bath > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] Aliasing problem > > SER does not create aliases automatically (only serweb does so when > creating a new user account). Only the content of location table gets > updated automatically from REGISTER messages. > > If the aliases are not correct then you can remove them using serctl and > create new ones. > > Jan. > > On 15-07 08:27, Dave Bath wrote: > > Hey Jan, > > > > I guessed this! Which is why I am confused. I have not created these > > aliases... all I have done is registered three different UAs with > three > > different usernames (admin, test1, test2). This is why I don't > > understand why there are all showing up. I think this may be why the > > extensions have stopped ringing correctly, but I don't know why it has > > happened. > > > > Any suggestions? Tests? Anything to do with net configuration? SER > > believing it is the same user agent registering each time? > > > > Once any, many thanks for all the support being shown here. > > > > Dave > > > > -----Original Message----- > > From: Jan Janak [mailto:jan@iptel.org] > > Sent: 15 July 2004 08:22 > > To: Dave Bath > > Cc: serusers(a)lists.iptel.org > > Subject: Re: [Serusers] Aliasing problem > > > > aliases are not recursive, in other words you cannot do something like > > this: alias1->alias2->alias3, SER would only translate alias1 into > > alias2 and then forward the request there. > > > > If you create several aliases for a single user (alias1->user1, > > alias1->user2, alias1->user3) then all of them should ring because SER > > will fork the INVITE. > > > > Jan. > > > > On 15-07 08:19, Dave Bath wrote: > > > Many thanks Jan. I rebuilt from the latest source fc RPMS, so I > have > > no > > > idea why serctl was inaccurate. Fixed now tho! > > > > > > My further problem with aliases might be my understanding, or > there's > > > something funny happening. Basically, when having 2 or 3 UAs, > calling > > > one of them results in random numbers of the other ones ringing as > > > well.. and usually the connecting party going straight to > "connected" > > > state rather than ringing. > > > > > > When I use serctl to examine the aliases, I see the following: > > > > > > [root@sip dave]# serctl alias show admin > > > <sip:admin@<ip1>:5060>;q=0.00;expires=3524 > > > <sip:test1@<ip2>:5060>;q=0.00;expires=2255 > > > <sip:test2@<ip3>:5060>;q=0.00;expires=3565 > > > > > > [root@sip dave]# serctl alias show test1 > > > <sip:admin@<ip1>:5060>;q=0.00;expires=2621 > > > > > > Am I completely misunderstanding how aliases work? But shouldn't > admin > > > show something like <sip:admin@<ip1>:5060 blah blah> and test1 show > > > something like <sip:test1@<ip2>:5060 blah blah>? > > > > > > Am I missing something? Any suggestions? > > > > > > D > > > > > > -----Original Message----- > > > From: Jan Janak [mailto:jan@iptel.org] > > > Sent: 15 July 2004 07:59 > > > To: Dave Bath > > > Cc: serusers(a)lists.iptel.org > > > Subject: Re: [Serusers] Aliasing problem > > > > > > Older versions of serctl contain a bug that make the inserted > aliases > > to > > > expire immediately, that has been fixed a long time ago, see: > > > > > > http://lists.iptel.org/pipermail/serusers/2004-January/004949.html > > > > > > Jan. > > > > > > On 14-07 19:40, Dave Bath wrote: > > > > Hey guys, > > > > > > > > > > > > > > > > I have been playing with SER for a few days now, and apart from > > having > > > > to rebuild all the RPMs to get it working on FC1 with mysql4 > (mysql4 > > > is > > > > apparently not officially supported in FC1 ?!) everything was > smooth > > > and > > > > dandy. Really enjoying using such a powerful and flexible > product. > > > > > > > > > > > > > > > > However, I have one problem, and I've done my best to trawl all > the > > > > groups and lists, and debug it myself and I cannot work out what > is > > > > going on - perhaps I just don't understand how it works properly. > I > > > am > > > > trying to set numerical aliases so that incoming routing can be > > > handled > > > > more easily by a PSTN gateway. I am trying the command: > > > > > > > > > > > > > > > > Serctl alias add 1000 sip:admin@<sipserver> > > > > > > > > > > > > > > > > I get a reply that the alias has been added (once a previous > message > > > on > > > > this list pointed out that I needed to add lookup("aliases"); to > > > > ser.cfg)! > > > > > > > > > > > > > > > > The problem is the mysql table is still empty - although serctl > says > > > > that the alias has been added, it doesn't seem to have been. When > I > > > try > > > > and call "1000" I get a 404 not found, but calling "admin" works > > fine. > > > > > > > > > > > > > > > > > > > Does anyone have any ideas?! > > > > > > > > > > > > > > > > Also, on a slight side note, I was assuming that the aliases are > > > > reboot-safe... they're stored in the database and will get > reloaded > > if > > > > ser is rebooted. Is this the case by default or does an option > need > > > to > > > > be enabled? > > > > > > > > > > > > > > > > Sorry for the long post. Many thanks to everyone who has worked > on > > > > this, and it would be fantastic to get this last bit sorted out. > > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > > > > > > > Dave > > > > > > > > > > > > > > > > Inmarsat Ltd > > > > > > > > Global Satellite Communications > > > > > > > > Regional BGAN Engineer > > > > > > > > > > > _______________________________________________ > > > > Serusers mailing list > > > > serusers(a)lists.iptel.org > > > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Serusers mailing list > > > serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers

1 0

RE: [Serusers] Aliasing problem
by Dave Bath 15 Jul '04

15 Jul '04

Ah! You genius!! Let me try that! Dave -----Original Message----- From: Jan Janak [mailto:jan@iptel.org] Sent: 15 July 2004 08:42 To: Dave Bath Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Aliasing problem Are you calling save("aliases") somewhere in the configuration file ? If so then you should replace it with save("location"), save("aliases") should never be called from the configuration file. Jan. On 15-07 08:40, Dave Bath wrote: > Ok this must be where I am confused... the only alias I have created is > "1000" and is mapped to sip:admin@sip.dev.inmarsat.com > > If I do a "serctl show alias admin" I get what I pasted below... I would > have expected to see the newly created "1000" alias... However, doing a > "serctl show alias 1000" does list admin.. as below > > [root@sip log]# serctl alias show 1000 > <sip:admin@sip.dev.inmarsat.com>;q=1.00;expires=31532649 > <sip:test1@161.30.211.131:5060>;q=0.00;expires=399 > > But it's also showing test1?!?!? WHY! Lol! I have never created any > aliases with test1. Similarly: > > [root@sip dave]# serctl alias show test1 > <sip:admin@<ip1>:5060>;q=0.00;expires=2621 > > Now as far as I know, that last command should have returned nothing, as > I have never created any aliases for test1. > > Also, I know that serweb creates aliases automatically - but it is set > to create numerical aliases. Besides, I am not using serweb to create > users, so that's just something else. > > Are all the registering UAs messing up the aliases somehow? This is > becoming very frustrating! > > Dave > > -----Original Message----- > From: Jan Janak [mailto:jan@iptel.org] > Sent: 15 July 2004 08:31 > To: Dave Bath > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] Aliasing problem > > SER does not create aliases automatically (only serweb does so when > creating a new user account). Only the content of location table gets > updated automatically from REGISTER messages. > > If the aliases are not correct then you can remove them using serctl and > create new ones. > > Jan. > > On 15-07 08:27, Dave Bath wrote: > > Hey Jan, > > > > I guessed this! Which is why I am confused. I have not created these > > aliases... all I have done is registered three different UAs with > three > > different usernames (admin, test1, test2). This is why I don't > > understand why there are all showing up. I think this may be why the > > extensions have stopped ringing correctly, but I don't know why it has > > happened. > > > > Any suggestions? Tests? Anything to do with net configuration? SER > > believing it is the same user agent registering each time? > > > > Once any, many thanks for all the support being shown here. > > > > Dave > > > > -----Original Message----- > > From: Jan Janak [mailto:jan@iptel.org] > > Sent: 15 July 2004 08:22 > > To: Dave Bath > > Cc: serusers(a)lists.iptel.org > > Subject: Re: [Serusers] Aliasing problem > > > > aliases are not recursive, in other words you cannot do something like > > this: alias1->alias2->alias3, SER would only translate alias1 into > > alias2 and then forward the request there. > > > > If you create several aliases for a single user (alias1->user1, > > alias1->user2, alias1->user3) then all of them should ring because SER > > will fork the INVITE. > > > > Jan. > > > > On 15-07 08:19, Dave Bath wrote: > > > Many thanks Jan. I rebuilt from the latest source fc RPMS, so I > have > > no > > > idea why serctl was inaccurate. Fixed now tho! > > > > > > My further problem with aliases might be my understanding, or > there's > > > something funny happening. Basically, when having 2 or 3 UAs, > calling > > > one of them results in random numbers of the other ones ringing as > > > well.. and usually the connecting party going straight to > "connected" > > > state rather than ringing. > > > > > > When I use serctl to examine the aliases, I see the following: > > > > > > [root@sip dave]# serctl alias show admin > > > <sip:admin@<ip1>:5060>;q=0.00;expires=3524 > > > <sip:test1@<ip2>:5060>;q=0.00;expires=2255 > > > <sip:test2@<ip3>:5060>;q=0.00;expires=3565 > > > > > > [root@sip dave]# serctl alias show test1 > > > <sip:admin@<ip1>:5060>;q=0.00;expires=2621 > > > > > > Am I completely misunderstanding how aliases work? But shouldn't > admin > > > show something like <sip:admin@<ip1>:5060 blah blah> and test1 show > > > something like <sip:test1@<ip2>:5060 blah blah>? > > > > > > Am I missing something? Any suggestions? > > > > > > D > > > > > > -----Original Message----- > > > From: Jan Janak [mailto:jan@iptel.org] > > > Sent: 15 July 2004 07:59 > > > To: Dave Bath > > > Cc: serusers(a)lists.iptel.org > > > Subject: Re: [Serusers] Aliasing problem > > > > > > Older versions of serctl contain a bug that make the inserted > aliases > > to > > > expire immediately, that has been fixed a long time ago, see: > > > > > > http://lists.iptel.org/pipermail/serusers/2004-January/004949.html > > > > > > Jan. > > > > > > On 14-07 19:40, Dave Bath wrote: > > > > Hey guys, > > > > > > > > > > > > > > > > I have been playing with SER for a few days now, and apart from > > having > > > > to rebuild all the RPMs to get it working on FC1 with mysql4 > (mysql4 > > > is > > > > apparently not officially supported in FC1 ?!) everything was > smooth > > > and > > > > dandy. Really enjoying using such a powerful and flexible > product. > > > > > > > > > > > > > > > > However, I have one problem, and I've done my best to trawl all > the > > > > groups and lists, and debug it myself and I cannot work out what > is > > > > going on - perhaps I just don't understand how it works properly. > I > > > am > > > > trying to set numerical aliases so that incoming routing can be > > > handled > > > > more easily by a PSTN gateway. I am trying the command: > > > > > > > > > > > > > > > > Serctl alias add 1000 sip:admin@<sipserver> > > > > > > > > > > > > > > > > I get a reply that the alias has been added (once a previous > message > > > on > > > > this list pointed out that I needed to add lookup("aliases"); to > > > > ser.cfg)! > > > > > > > > > > > > > > > > The problem is the mysql table is still empty - although serctl > says > > > > that the alias has been added, it doesn't seem to have been. When > I > > > try > > > > and call "1000" I get a 404 not found, but calling "admin" works > > fine. > > > > > > > > > > > > > > > > > > > Does anyone have any ideas?! > > > > > > > > > > > > > > > > Also, on a slight side note, I was assuming that the aliases are > > > > reboot-safe... they're stored in the database and will get > reloaded > > if > > > > ser is rebooted. Is this the case by default or does an option > need > > > to > > > > be enabled? > > > > > > > > > > > > > > > > Sorry for the long post. Many thanks to everyone who has worked > on > > > > this, and it would be fantastic to get this last bit sorted out. > > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > > > > > > > Dave > > > > > > > > > > > > > > > > Inmarsat Ltd > > > > > > > > Global Satellite Communications > > > > > > > > Regional BGAN Engineer > > > > > > > > > > > _______________________________________________ > > > > Serusers mailing list > > > > serusers(a)lists.iptel.org > > > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Serusers mailing list > > > serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers

1 0

RE: [Serusers] Aliasing problem
by Dave Bath 15 Jul '04

15 Jul '04

Ok this must be where I am confused... the only alias I have created is "1000" and is mapped to sip:admin@sip.dev.inmarsat.com If I do a "serctl show alias admin" I get what I pasted below... I would have expected to see the newly created "1000" alias... However, doing a "serctl show alias 1000" does list admin.. as below [root@sip log]# serctl alias show 1000 <sip:admin@sip.dev.inmarsat.com>;q=1.00;expires=31532649 <sip:test1@161.30.211.131:5060>;q=0.00;expires=399 But it's also showing test1?!?!? WHY! Lol! I have never created any aliases with test1. Similarly: [root@sip dave]# serctl alias show test1 <sip:admin@<ip1>:5060>;q=0.00;expires=2621 Now as far as I know, that last command should have returned nothing, as I have never created any aliases for test1. Also, I know that serweb creates aliases automatically - but it is set to create numerical aliases. Besides, I am not using serweb to create users, so that's just something else. Are all the registering UAs messing up the aliases somehow? This is becoming very frustrating! Dave -----Original Message----- From: Jan Janak [mailto:jan@iptel.org] Sent: 15 July 2004 08:31 To: Dave Bath Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Aliasing problem SER does not create aliases automatically (only serweb does so when creating a new user account). Only the content of location table gets updated automatically from REGISTER messages. If the aliases are not correct then you can remove them using serctl and create new ones. Jan. On 15-07 08:27, Dave Bath wrote: > Hey Jan, > > I guessed this! Which is why I am confused. I have not created these > aliases... all I have done is registered three different UAs with three > different usernames (admin, test1, test2). This is why I don't > understand why there are all showing up. I think this may be why the > extensions have stopped ringing correctly, but I don't know why it has > happened. > > Any suggestions? Tests? Anything to do with net configuration? SER > believing it is the same user agent registering each time? > > Once any, many thanks for all the support being shown here. > > Dave > > -----Original Message----- > From: Jan Janak [mailto:jan@iptel.org] > Sent: 15 July 2004 08:22 > To: Dave Bath > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] Aliasing problem > > aliases are not recursive, in other words you cannot do something like > this: alias1->alias2->alias3, SER would only translate alias1 into > alias2 and then forward the request there. > > If you create several aliases for a single user (alias1->user1, > alias1->user2, alias1->user3) then all of them should ring because SER > will fork the INVITE. > > Jan. > > On 15-07 08:19, Dave Bath wrote: > > Many thanks Jan. I rebuilt from the latest source fc RPMS, so I have > no > > idea why serctl was inaccurate. Fixed now tho! > > > > My further problem with aliases might be my understanding, or there's > > something funny happening. Basically, when having 2 or 3 UAs, calling > > one of them results in random numbers of the other ones ringing as > > well.. and usually the connecting party going straight to "connected" > > state rather than ringing. > > > > When I use serctl to examine the aliases, I see the following: > > > > [root@sip dave]# serctl alias show admin > > <sip:admin@<ip1>:5060>;q=0.00;expires=3524 > > <sip:test1@<ip2>:5060>;q=0.00;expires=2255 > > <sip:test2@<ip3>:5060>;q=0.00;expires=3565 > > > > [root@sip dave]# serctl alias show test1 > > <sip:admin@<ip1>:5060>;q=0.00;expires=2621 > > > > Am I completely misunderstanding how aliases work? But shouldn't admin > > show something like <sip:admin@<ip1>:5060 blah blah> and test1 show > > something like <sip:test1@<ip2>:5060 blah blah>? > > > > Am I missing something? Any suggestions? > > > > D > > > > -----Original Message----- > > From: Jan Janak [mailto:jan@iptel.org] > > Sent: 15 July 2004 07:59 > > To: Dave Bath > > Cc: serusers(a)lists.iptel.org > > Subject: Re: [Serusers] Aliasing problem > > > > Older versions of serctl contain a bug that make the inserted aliases > to > > expire immediately, that has been fixed a long time ago, see: > > > > http://lists.iptel.org/pipermail/serusers/2004-January/004949.html > > > > Jan. > > > > On 14-07 19:40, Dave Bath wrote: > > > Hey guys, > > > > > > > > > > > > I have been playing with SER for a few days now, and apart from > having > > > to rebuild all the RPMs to get it working on FC1 with mysql4 (mysql4 > > is > > > apparently not officially supported in FC1 ?!) everything was smooth > > and > > > dandy. Really enjoying using such a powerful and flexible product. > > > > > > > > > > > > However, I have one problem, and I've done my best to trawl all the > > > groups and lists, and debug it myself and I cannot work out what is > > > going on - perhaps I just don't understand how it works properly. I > > am > > > trying to set numerical aliases so that incoming routing can be > > handled > > > more easily by a PSTN gateway. I am trying the command: > > > > > > > > > > > > Serctl alias add 1000 sip:admin@<sipserver> > > > > > > > > > > > > I get a reply that the alias has been added (once a previous message > > on > > > this list pointed out that I needed to add lookup("aliases"); to > > > ser.cfg)! > > > > > > > > > > > > The problem is the mysql table is still empty - although serctl says > > > that the alias has been added, it doesn't seem to have been. When I > > try > > > and call "1000" I get a 404 not found, but calling "admin" works > fine. > > > > > > > > > > > > > > Does anyone have any ideas?! > > > > > > > > > > > > Also, on a slight side note, I was assuming that the aliases are > > > reboot-safe... they're stored in the database and will get reloaded > if > > > ser is rebooted. Is this the case by default or does an option need > > to > > > be enabled? > > > > > > > > > > > > Sorry for the long post. Many thanks to everyone who has worked on > > > this, and it would be fantastic to get this last bit sorted out. > > > > > > > > > > > > Cheers, > > > > > > > > > > > > Dave > > > > > > > > > > > > Inmarsat Ltd > > > > > > Global Satellite Communications > > > > > > Regional BGAN Engineer > > > > > > > > _______________________________________________ > > > Serusers mailing list > > > serusers(a)lists.iptel.org > > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > > > > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers

2 1

RE: [Serusers] Aliasing problem
by Dave Bath 15 Jul '04

15 Jul '04

Hey Jan, I guessed this! Which is why I am confused. I have not created these aliases... all I have done is registered three different UAs with three different usernames (admin, test1, test2). This is why I don't understand why there are all showing up. I think this may be why the extensions have stopped ringing correctly, but I don't know why it has happened. Any suggestions? Tests? Anything to do with net configuration? SER believing it is the same user agent registering each time? Once any, many thanks for all the support being shown here. Dave -----Original Message----- From: Jan Janak [mailto:jan@iptel.org] Sent: 15 July 2004 08:22 To: Dave Bath Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Aliasing problem aliases are not recursive, in other words you cannot do something like this: alias1->alias2->alias3, SER would only translate alias1 into alias2 and then forward the request there. If you create several aliases for a single user (alias1->user1, alias1->user2, alias1->user3) then all of them should ring because SER will fork the INVITE. Jan. On 15-07 08:19, Dave Bath wrote: > Many thanks Jan. I rebuilt from the latest source fc RPMS, so I have no > idea why serctl was inaccurate. Fixed now tho! > > My further problem with aliases might be my understanding, or there's > something funny happening. Basically, when having 2 or 3 UAs, calling > one of them results in random numbers of the other ones ringing as > well.. and usually the connecting party going straight to "connected" > state rather than ringing. > > When I use serctl to examine the aliases, I see the following: > > [root@sip dave]# serctl alias show admin > <sip:admin@<ip1>:5060>;q=0.00;expires=3524 > <sip:test1@<ip2>:5060>;q=0.00;expires=2255 > <sip:test2@<ip3>:5060>;q=0.00;expires=3565 > > [root@sip dave]# serctl alias show test1 > <sip:admin@<ip1>:5060>;q=0.00;expires=2621 > > Am I completely misunderstanding how aliases work? But shouldn't admin > show something like <sip:admin@<ip1>:5060 blah blah> and test1 show > something like <sip:test1@<ip2>:5060 blah blah>? > > Am I missing something? Any suggestions? > > D > > -----Original Message----- > From: Jan Janak [mailto:jan@iptel.org] > Sent: 15 July 2004 07:59 > To: Dave Bath > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] Aliasing problem > > Older versions of serctl contain a bug that make the inserted aliases to > expire immediately, that has been fixed a long time ago, see: > > http://lists.iptel.org/pipermail/serusers/2004-January/004949.html > > Jan. > > On 14-07 19:40, Dave Bath wrote: > > Hey guys, > > > > > > > > I have been playing with SER for a few days now, and apart from having > > to rebuild all the RPMs to get it working on FC1 with mysql4 (mysql4 > is > > apparently not officially supported in FC1 ?!) everything was smooth > and > > dandy. Really enjoying using such a powerful and flexible product. > > > > > > > > However, I have one problem, and I've done my best to trawl all the > > groups and lists, and debug it myself and I cannot work out what is > > going on - perhaps I just don't understand how it works properly. I > am > > trying to set numerical aliases so that incoming routing can be > handled > > more easily by a PSTN gateway. I am trying the command: > > > > > > > > Serctl alias add 1000 sip:admin@<sipserver> > > > > > > > > I get a reply that the alias has been added (once a previous message > on > > this list pointed out that I needed to add lookup("aliases"); to > > ser.cfg)! > > > > > > > > The problem is the mysql table is still empty - although serctl says > > that the alias has been added, it doesn't seem to have been. When I > try > > and call "1000" I get a 404 not found, but calling "admin" works fine. > > > > > > > > > Does anyone have any ideas?! > > > > > > > > Also, on a slight side note, I was assuming that the aliases are > > reboot-safe... they're stored in the database and will get reloaded if > > ser is rebooted. Is this the case by default or does an option need > to > > be enabled? > > > > > > > > Sorry for the long post. Many thanks to everyone who has worked on > > this, and it would be fantastic to get this last bit sorted out. > > > > > > > > Cheers, > > > > > > > > Dave > > > > > > > > Inmarsat Ltd > > > > Global Satellite Communications > > > > Regional BGAN Engineer > > > > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers

2 1

RE: [Serusers] Aliasing problem
by Dave Bath 15 Jul '04

15 Jul '04

Many thanks Jan. I rebuilt from the latest source fc RPMS, so I have no idea why serctl was inaccurate. Fixed now tho! My further problem with aliases might be my understanding, or there's something funny happening. Basically, when having 2 or 3 UAs, calling one of them results in random numbers of the other ones ringing as well.. and usually the connecting party going straight to "connected" state rather than ringing. When I use serctl to examine the aliases, I see the following: [root@sip dave]# serctl alias show admin <sip:admin@<ip1>:5060>;q=0.00;expires=3524 <sip:test1@<ip2>:5060>;q=0.00;expires=2255 <sip:test2@<ip3>:5060>;q=0.00;expires=3565 [root@sip dave]# serctl alias show test1 <sip:admin@<ip1>:5060>;q=0.00;expires=2621 Am I completely misunderstanding how aliases work? But shouldn't admin show something like <sip:admin@<ip1>:5060 blah blah> and test1 show something like <sip:test1@<ip2>:5060 blah blah>? Am I missing something? Any suggestions? D -----Original Message----- From: Jan Janak [mailto:jan@iptel.org] Sent: 15 July 2004 07:59 To: Dave Bath Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Aliasing problem Older versions of serctl contain a bug that make the inserted aliases to expire immediately, that has been fixed a long time ago, see: http://lists.iptel.org/pipermail/serusers/2004-January/004949.html Jan. On 14-07 19:40, Dave Bath wrote: > Hey guys, > > > > I have been playing with SER for a few days now, and apart from having > to rebuild all the RPMs to get it working on FC1 with mysql4 (mysql4 is > apparently not officially supported in FC1 ?!) everything was smooth and > dandy. Really enjoying using such a powerful and flexible product. > > > > However, I have one problem, and I've done my best to trawl all the > groups and lists, and debug it myself and I cannot work out what is > going on - perhaps I just don't understand how it works properly. I am > trying to set numerical aliases so that incoming routing can be handled > more easily by a PSTN gateway. I am trying the command: > > > > Serctl alias add 1000 sip:admin@<sipserver> > > > > I get a reply that the alias has been added (once a previous message on > this list pointed out that I needed to add lookup("aliases"); to > ser.cfg)! > > > > The problem is the mysql table is still empty - although serctl says > that the alias has been added, it doesn't seem to have been. When I try > and call "1000" I get a 404 not found, but calling "admin" works fine. > > > > Does anyone have any ideas?! > > > > Also, on a slight side note, I was assuming that the aliases are > reboot-safe... they're stored in the database and will get reloaded if > ser is rebooted. Is this the case by default or does an option need to > be enabled? > > > > Sorry for the long post. Many thanks to everyone who has worked on > this, and it would be fantastic to get this last bit sorted out. > > > > Cheers, > > > > Dave > > > > Inmarsat Ltd > > Global Satellite Communications > > Regional BGAN Engineer > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers

2 1

[Serusers] Aliasing problem
by Dave Bath 15 Jul '04

15 Jul '04

Hey guys, I have been playing with SER for a few days now, and apart from having to rebuild all the RPMs to get it working on FC1 with mysql4 (mysql4 is apparently not officially supported in FC1 ?!) everything was smooth and dandy. Really enjoying using such a powerful and flexible product. However, I have one problem, and I've done my best to trawl all the groups and lists, and debug it myself and I cannot work out what is going on - perhaps I just don't understand how it works properly. I am trying to set numerical aliases so that incoming routing can be handled more easily by a PSTN gateway. I am trying the command: Serctl alias add 1000 sip:admin@<sipserver> I get a reply that the alias has been added (once a previous message on this list pointed out that I needed to add lookup("aliases"); to ser.cfg)! The problem is the mysql table is still empty - although serctl says that the alias has been added, it doesn't seem to have been. When I try and call "1000" I get a 404 not found, but calling "admin" works fine. Does anyone have any ideas?! Also, on a slight side note, I was assuming that the aliases are reboot-safe... they're stored in the database and will get reloaded if ser is rebooted. Is this the case by default or does an option need to be enabled? Sorry for the long post. Many thanks to everyone who has worked on this, and it would be fantastic to get this last bit sorted out. Cheers, Dave Inmarsat Ltd Global Satellite Communications Regional BGAN Engineer

4 3

RE: [Serusers] Aliasing problem
by Dave Bath 15 Jul '04

15 Jul '04

Hi Jan, thanks for this response. However, the problem is that if I leave the value in serctl as default, the aliases are not inserted correctly! Serctl reports a successful insertion, but they are not. Changing the value in serctl down as suggested fixes the problem. Any ideas? D -----Original Message----- From: Jan Janak [mailto:jan@iptel.org] Sent: 15 July 2004 07:33 To: Dave Bath; serusers(a)lists.iptel.org Subject: Re: [Serusers] Aliasing problem Yes, it was a bug in serctl but it has been fixed. Update your serctl, the aliases are valid for 30 years. Jan. On 14-07 22:57, Andrei Pelinescu-Onciul wrote: > On Jul 14, 2004 at 20:45, Dave Bath <dave(a)fuuz.com> wrote: > > Hey thanks, that did fix it. Now if I do a serctl show alias 1000 I see > > Admin listed, and it's listed under the "Your Aliases" section of > > serweb. I still don't understand why there wasn't an error thrown back > > by serctl. Does anyone know which field from the database is needed, as > > conceivably someone might have a phone number for longer than a year, > > and I don't want to have to renew all the aliases... > > What version of ser are you using? > There was a bug related to the alias expiration time, but AFAIK it was > fixed long time ago. > > Andrei > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers

1 0

RE: [Serusers] Aliasing problem
by Dave Bath 15 Jul '04

15 Jul '04

Hey thanks, that did fix it. Now if I do a serctl show alias 1000 I see Admin listed, and it's listed under the "Your Aliases" section of serweb. I still don't understand why there wasn't an error thrown back by serctl. Does anyone know which field from the database is needed, as conceivably someone might have a phone number for longer than a year, and I don't want to have to renew all the aliases... Best regards, Dave ________________________________ From: Ezequiel Colombo [mailto:ecolombo@arcotel.net] Sent: 14 July 2004 20:17 To: Dave Bath; serusers(a)lists.iptel.org Subject: Re: [Serusers] Aliasing problem FOREVER_REL contain the value used by serctl to set the Expires time of the contact alias added. If this value is too large the value result a hugh value for the column type of the aliases table. ----- Original Message ----- From: Dave Bath <mailto:dave@fuuz.com> To: serusers(a)lists.iptel.org Sent: Wednesday, July 14, 2004 4:01 PM Subject: [Serusers] Aliasing problem Hey Ezequiel, Many thanks for the quick response! Yeah, sorry, I should have mentioned I already have persistent storage for the user tables - they're all stored using mode2, I was just checking with all the references to "aliases stored in cache" that they were actually written to the db as well. Could you explain what the FOREVER_REL value is? Why would the value be too high? Too large a number of the type of storage in the mysql table? Also, does anyone know why the serctl script says the alias was added, but it doesn't seem to have been..? Many thanks again everyone, D ________________________________ From: Ezequiel Colombo [mailto:ecolombo@arcotel.net] Sent: 14 July 2004 19:54 To: Dave Bath; serusers(a)lists.iptel.org Subject: Re: [Serusers] Aliasing problem Dave, you must turn no the persistent storage of the usrloc table. After this the contacts added in the memory table can be dumped to mysql. You can also check in the script serctl if the value of the variable FOREVER_REL is appropiate or is too high for your mysql aliases table and cause the INSERT to fail. In my network i have reduced this value to FOREVER_REL=31536000 (one year). ... FROM README FILE OF USRLOC MODULE ... 1.3.10. db_mode (integer) The usrloc module can utilize database for persistent contact storage. If you use database, your contacts will survive machine restarts or sw crashes. The disadvantage is that accessing database can be very time consuming. Therefore, usrloc module implements three database accessing modes: * 0 - This disables database completely. Only memory will be used. Contacts will not survive restart. Use this value if you need a really fast usrloc and contact persistence is not necessarry or is provided by other means. * 1 - Write-Through scheme. All changes to usrloc are immediately reflected in database too. This is very slow, but very reliable. Use this scheme if speed is not your priority but need to make sure that no registered contacts will be lost during crash or reboot. * 2 - Write-Back scheme. This is a combination of previous two schemes. All changes are made to memory and database synchronization is done in the timer. The timer deletes all expired contacts and flushes all modified or new contacts to database. Use this scheme if you encounter high-load peaks and want them to process as fast as possible. The mode will not help at all if the load is high all the time. Also, latency of this mode is much lower than latency of mode 1, but slightly higher than latency of mode 0. Warning In case of crash or restart contacts that are in memory only and haven't been flushed yet will get lost. If you want minimize the risk, use shorter timer interval. Default value is 0. Example 1-10. Set db_mode parameter ... modparam("usrloc", "db_mode", 2) ... ----- Original Message ----- From: Dave Bath <mailto:dave@fuuz.com> To: serusers(a)lists.iptel.org Sent: Wednesday, July 14, 2004 3:40 PM Subject: [Serusers] Aliasing problem Hey guys, I have been playing with SER for a few days now, and apart from having to rebuild all the RPMs to get it working on FC1 with mysql4 (mysql4 is apparently not officially supported in FC1 ?!) everything was smooth and dandy. Really enjoying using such a powerful and flexible product. However, I have one problem, and I've done my best to trawl all the groups and lists, and debug it myself and I cannot work out what is going on - perhaps I just don't understand how it works properly. I am trying to set numerical aliases so that incoming routing can be handled more easily by a PSTN gateway. I am trying the command: Serctl alias add 1000 sip:admin@<sipserver> I get a reply that the alias has been added (once a previous message on this list pointed out that I needed to add lookup("aliases"); to ser.cfg)! The problem is the mysql table is still empty - although serctl says that the alias has been added, it doesn't seem to have been. When I try and call "1000" I get a 404 not found, but calling "admin" works fine. Does anyone have any ideas?! Also, on a slight side note, I was assuming that the aliases are reboot-safe... they're stored in the database and will get reloaded if ser is rebooted. Is this the case by default or does an option need to be enabled? Sorry for the long post. Many thanks to everyone who has worked on this, and it would be fantastic to get this last bit sorted out. Cheers, Dave Inmarsat Ltd Global Satellite Communications Regional BGAN Engineer ________________________________ _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers ________________________________ _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

3 2

RE: [Serusers] Aliasing problem
by Dave Bath 15 Jul '04

15 Jul '04

Hey Charles, No, it's a machine with both ser and mysql running. I don't quite understand... making the change suggested by Ezequiel for FOREVER_REL did fix it, but I can only guess this is because the original value was too large for mysql to store. Does anyone happen to know (before I start delving into the database) where the FOREVER_REL value is stored in the db so I can check the params of that field? On a bizarre other turn in events (which I may have to repost as a new subject if nobody notices this one...) since upgrading to mysql4 (this may not be the reason, but it certainly seems that way...) extensions no longer ring! Or they ring only in one direction... usually what happens is the phone moves straight to the "connected" state, but the called extension never rings. This has only started happening now... it was working perfectly before. Any help would be very very much appreciated! D ________________________________ From: Charles Galea [mailto:charles.galea@maltacom.com] Sent: 15 July 2004 06:10 To: Dave Bath; serusers(a)lists.iptel.org Subject: Re: [Serusers] Aliasing problem Hi Dave, We've been through this problem; in our case it happened when we were using a seperate machine for mysql database.......are you doing the same? Charles ----- Original Message ----- From: Dave Bath <mailto:dave@fuuz.com> To: serusers(a)lists.iptel.org Sent: Wednesday, July 14, 2004 20:40 Subject: [Serusers] Aliasing problem Hey guys, I have been playing with SER for a few days now, and apart from having to rebuild all the RPMs to get it working on FC1 with mysql4 (mysql4 is apparently not officially supported in FC1 ?!) everything was smooth and dandy. Really enjoying using such a powerful and flexible product. However, I have one problem, and I've done my best to trawl all the groups and lists, and debug it myself and I cannot work out what is going on - perhaps I just don't understand how it works properly. I am trying to set numerical aliases so that incoming routing can be handled more easily by a PSTN gateway. I am trying the command: Serctl alias add 1000 sip:admin@<sipserver> I get a reply that the alias has been added (once a previous message on this list pointed out that I needed to add lookup("aliases"); to ser.cfg)! The problem is the mysql table is still empty - although serctl says that the alias has been added, it doesn't seem to have been. When I try and call "1000" I get a 404 not found, but calling "admin" works fine. Does anyone have any ideas?! Also, on a slight side note, I was assuming that the aliases are reboot-safe... they're stored in the database and will get reloaded if ser is rebooted. Is this the case by default or does an option need to be enabled? Sorry for the long post. Many thanks to everyone who has worked on this, and it would be fantastic to get this last bit sorted out. Cheers, Dave Inmarsat Ltd Global Satellite Communications Regional BGAN Engineer ________________________________ _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

1 0

[Serusers] forward_msg: no 2nd via found in reply
by Cyprien Simons 15 Jul '04

15 Jul '04

Hi everybody, I'm trying to use Asterisk as SUA and SER as SIP router. But Asterisk doesn't succeed to register the Asterisk user to SER... the standard error output tell me: "ERROR: forward_msg: no 2nd via found in reply" the SIP message looks like: to 193.175.133.19:5060 Retransmitting #5 (no NAT): REGISTER sip:potemkin.fokus.fraunhofer.de SIP/2.0 Via: SIP/2.0/UDP 193.175.133.19:5060;branch=z9hG4bK625558ec From: <sip:cys@potemkin.fokus.fraunhofer.de>;tag=as238e1f29 To: <sip:cys@potemkin.fokus.fraunhofer.de> Call-ID: 6b8b4567327b23c6643c986966334873(a)193.175.133.19 CSeq: 102 REGISTER User-Agent: Asterisk PBX Expires: 120 Contact: <sip:1234@193.175.133.19> Event: registration Content-Length: 0 and the configuration file is like: ###main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if ( msg:len > max_len ) { sl_send_reply("513", "Message too big"); break; }; record_route(); # Do strict routing if pre-loaded route headers present loose_route(); # message should be from 127.0.0.1 or # from other listening address if (src_ip==127.0.0.1) { if (method=="REGISTER") { save("location"); break; }; if (uri == myself) { # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; # forward to current uri now if (!t_relay()) { sl_reply_error(); }; } else if (src_ip == myself) { # this is a request from local domain # but not from 127.0.0.1, must be from UA if (method=="REGISTER") { # register message, save it and forward to # security server save("location"); forward (127.0.0.1, 4050); break; }; forward (127.0.0.1, 4050); break; }; } I'm using ser 0.8.12, SuSE 9.1, Asterisk 0.9.1 I am quite new on SER, and I am trying to pursue the work of another person, so if something in it seems stupid, don't hesitate to tell me so... Cyprien

4 3

← Newer
1
...
26
27
28
29
30
31
32
...
45
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users July 2004