So I have two ITSP gateways configured. They each have different credentials and are set to register on initialization. Their status right now:
Identifier Registration Status sipconnect.internode.on.net [Axxxxxxx] AUTHENTICATING sipconnect.internode.on.net [Bxxxxxxx] AUTHENTICATING After restarting the services they both say AUTHENTICATED for a few minutes then go back to AUTHENTICATING and then after a few more minutes back to AUTHENTICATED again. If I make a test inbound call, which fails, it changes it again. The credentials are added under "ITSP Account" in the each gateway's configuration. I assume this is what you mean by sip trunk? These sip trunk gateways have five dialing rules added to them so people can use them to dial out for local, long distance, toll free calling etc. They also have 'transform extension' enabled under Caller ID, which takes the last 2 digits of the user's extension and adds it to the first part of the caller ID prefix. I have checked with Internode and they say they can see the INVITE being sent to us and immediately after they get the 'loop detected' messages every half a second and then they block us for five minutes. I didn't set up the pfsense nat. Perhaps I should try removing the port 5080 port forward and add it again. I'll also try disabling the trunks, flushing the nat tables, and re-enabling the trunks and see how we go. It really feels to me like sipxbridge is confusing the two trunks somehow. I don't think Internode provide secondary IP addresses for their sip service but I'll ask them, and see if it makes a difference. I wonder if adding an alias in /etc/hosts to the itsp and using the alias for the second gateway would overcome the problem. I might try that too. Thanks Jesse On 20/08/2010, at 5:19 PM, Tony Graziano wrote: > If memory serves me well (it may not, but it's been less than a week), this > is perfectly duplicatable and works for me. > > Example: > > ITSP1 create account, register and send/receive calls to ITSP server NY. > ITSP2 create secondary (or subaccount), register and send/receive calls to > ITSP server NY. > > BOTH accounts would have to use DIFFERENT credentials in other for this to > work with one ITSP. Please check them. > > It is assumed you are not creating "gateways" as Ip addresses (like a FXO/PRI > would), but are creating sip trunks. > > Did you deviate from a standard pfsense template in some way? > > If it were me (and its not), I would disable the trunks, clear my state table > in pfsense, and re-enable my trunks, assuming "register on initialization is > enabled on them too. > > Since they show "changes" in authenticating, it might be more productive to > re-examine your itsp credentials and compare both gateway configurations. > > > newyork.voip.ms [main account number] AUTHENTICATED > newyork.voip.ms [sub account number] AUTHENTICATED > > See above, working configuration with this provider. > > Does your ITSP have any insight as to what the issue might be? Broadworks > deployments seem to be "hit or miss", so perhaps following up with them for > information on what they are seeing might be fruitful as well. > > The above example is ALSO behind NAT (pfsense). > > On Fri, Aug 20, 2010 at 3:28 AM, Todd Hodgen <[email protected]> wrote: > I seem to recall early on with sipxbridge that if you had multiple gateways > pointed to the same IP address, that it created problems. Not like this, but > that they were treated like one trunk group. This may have been cleared up > in a later release, I don’t recall seeing any more discussion of it, however > that discussion caused me to create a workaround an installation during that > timeframe. > > > I can state that I have one site that uses the same ITSP for three different > accounts, resulting in three different gateways. However, I have each one > routed to a different IP address at the ITSP. > > > Gateway one – xxx.xxx.xxx.1 > > Gateway two – xxx.xxx.xxx.2 > > Gateway three – xxx.xxx.xxx.3 > > > It works, there are no issues in this specific design and implementation. > You might want to check to see if your ITSP can accommodate that for you. > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Tony Graziano > Sent: Friday, August 20, 2010 12:21 AM > To: Jesse Reynolds > Cc: [email protected] users > Subject: Re: [sipx-users] loop detected in sipxbridge after adding second > ITSP to the internal SBC > > > There should be no reason that I can think of that this would not work.I saw > one last week with 5 or 6 registrations to the same itsp. > > > What version of sipx is it? > > On Fri, Aug 20, 2010 at 1:04 AM, Jesse Reynolds <[email protected]> wrote: > > Hello > > I have sipxecs behind a pfsense router doing NAT. I had one ITSP account on > it with a 100 number range working well. I've just added a second gateway > with a second ITSP account to the system. They are both using the same bridge > - 'internal SBC'. They are also both using the same ITSP - Internode > Nodephone (who run a broadworks system). > > As soon as I added the second gateway and ITSP account the first one stopped > working, and the second doesn't work either. Incoming calls are received and > initially ring an extension however the caller gets a rejection. Subsequent > calls are rejected. > > Looking at the logs, something appears to be looping as there's a lot of "482 > Loop detected" messages. Even after hanging up both ends there is still this > 'loop detected' message being written to the sipxbridge.log file over and > over. > > When I look at the UI - Diagnostics / Internal SBC Statistics, most of the > time the two SIP trunks have a registration status of "AUTHENTICATING", with > brief periods of "AUTHENTICATED". > > Is this a limitation of sipx? That I can't connect to two SIP accounts at the > same ITSP from the same server? > > We have an Epygi IP PBX at a different site that is happily registering with > two different SIP accounts both at Internode, so this can work. > > Thank you > Jesse > > Jesse Reynolds > Virtual Artists Pty Ltd - http://www.va.com.au/ > Phone: 08 7120 7134 (Adelaide) or 02 9043 2288 (Sydney) Mobile: 0414 669 > 790 > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > Why do mathematicians always confuse Halloween and Christmas? > Because 31 Oct = 25 Dec. > > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > Why do mathematicians always confuse Halloween and Christmas? > Because 31 Oct = 25 Dec. > Jesse Reynolds Virtual Artists Pty Ltd - http://www.va.com.au/ Phone: 08 7120 7134 (Adelaide) or 02 9043 2288 (Sydney) Mobile: 0414 669 790
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
