Vitelity Registrations

[Steve B]

Hi Guys,

 

I am trying to get a stable setup with Vitelity registrations but it seams that it always gets a 408 error sometimes once every two minutes for an hour. My trunk setup is below:

 

# Trunk 18 in domain xxx.xxx.xxx.xxx
Name: Vitelity Inbound
Type: register
To: sip
RegPass: ********
Direction: 
Disabled: false
Global: false
Display: Vitelity Inbound
RegAccount: username
RegRegistrar: inbound28.vitelity.net
RegKeep: 
RegUser: username
Icid: 
Require: 
OutboundProxy: 
Ani: 
DialExtension: 112
Prefix: 
Trusted: false
AcceptRedirect: false
RfcRtp: false
Analog: false
SendEmail: true
UseUuid: false
Ring180: false
Failover: never
HeaderRequestUri: {request-uri}
HeaderFrom: {trunk}
HeaderTo: {request-uri}
HeaderPai: 
HeaderPpi: 
HeaderRpi: {from}
HeaderPrivacy: 
HeaderRpiCharging: 
BlockCidPrefix: 
Glob: nanpa
RequestTimeout: 
Codecs: 0 8 18
CodecLock: true
DtmfMode: 
Expires: 3600
FromUser: 
Tel: true
TranscodeDtmf: true
AssociatedAddresses: 
InterOffice: false
DialPlan: 
UseEpid: false
CidUpdate: 
Ignore18xSDP: false
UserHdr: 
Diversion: 
Colines: 
DialogPermission: 

 

 

It doesn't make a difference if it is a public IP with no router or behind NAT, same result. If I use a gateway on my server, I do not have a problem but I am working on stabilizing it for a client behind a NAT firewall so I need to get the registration working. Has anybody got registration with Vitelity to work with snomONE?

[Vodia PBX]

At first glance I would say, why is there no outbound proxy? If you don't use a outbound proxy, the PBX will accept inbound traffic from any location in the internet, including the friendly scanner. There should actually a be warning popping up if you try to save a trunk and don't have the outbound proxy set.

 

Then the next point is that SIP uses a lot of DNS queries. Probably the DNS is not fast enough, and then the registration times out. You can reduce the problem by setting the outbound proxy to sip:inbound28.vitelity.net:5060, which means that it only performs DNS A and DNS AAAA queries (not our idea, that's the SIP standard). Or you forget about DNS completely and use sip:66.241.99.27:5060. Then there will be no DNS query at all.

[Steve B]

At first glance I would say, why is there no outbound proxy? If you don't use a outbound proxy, the PBX will accept inbound traffic from any location in the internet, including the friendly scanner. There should actually a be warning popping up if you try to save a trunk and don't have the outbound proxy set.

 

Then the next point is that SIP uses a lot of DNS queries. Probably the DNS is not fast enough, and then the registration times out. You can reduce the problem by setting the outbound proxy to sip:inbound28.vitelity.net:5060, which means that it only performs DNS A and DNS AAAA queries (not our idea, that's the SIP standard). Or you forget about DNS completely and use sip:66.241.99.27:5060. Then there will be no DNS query at all.

 

Thank you for the information on the outbound proxy, that was the latest change I made to see if it helped, in which it didn't. So I re assigned the out bound proxy.

 

So if I just use the IP address without specifying sip and the port it still does a DNS query? I will set it up the way you told me and see how it goes, thank you for the help.

[Vodia PBX]

So if I just use the IP address without specifying sip and the port it still does a DNS query? I will set it up the way you told me and see how it goes, thank you for the help.

 

In this case you really should use the outbound proxy. There is no point accepting traffic from anywhere from the Internet. If you put just the IP address, it will not perform any DNS query. If the registration is still not stable, it was not the DNS. Then we have to search for problems with the Internet connection (then it will be time for PCAP).

[Steve B]

It seems to be better now only losing registration about once every hour now that I put in the exact syntax you specified, will keep monitoring it.

 

Last night I tried using just the IP before seeing your post for using sip:66.241.99.27:5060 and it didn't hold up. Keeping my fingers crossed.

 

I added the out bound proxy this morning.

[Pablo]

It seems to be better now only losing registration about once every hour now that I put in the exact syntax you specified, will keep monitoring it.

 

Last night I tried using just the IP before seeing your post for using sip:66.241.99.27:5060 and it didn't hold up. Keeping my fingers crossed.

 

I added the out bound proxy this morning.

 

Did you ever get this to work? Does the trunk require an ANI?

[Steve B]

Did you ever get this to work? Does the trunk require an ANI?

 

I have it working pretty good, dialing out is sometimes quick and sometimes a 10 second wait. Here is my IP registration setup:

 

# Trunk 17
Name: Vitelity
Type: proxy
To: sip
RegPass: ********
Direction: 
Disabled: false
Global: false
Display: 
RegAccount: 
RegRegistrar: inbound.server.net
RegKeep: 
RegUser: 
Icid: 
Require: 
OutboundProxy: out.bou.nd.ip
Ani: 
DialExtension: 112
Prefix: 
Trusted: false
AcceptRedirect: false
RfcRtp: false
Analog: false
SendEmail: 
UseUuid: false
Ring180: false
Failover: never
HeaderRequestUri: {request-uri}
HeaderFrom: {from}
HeaderTo: {to}
HeaderPai: {trunk}
HeaderPpi: 
HeaderRpi: 
HeaderPrivacy: 
HeaderRpiCharging: 
BlockCidPrefix: 
Glob: 
RequestTimeout: 
Codecs: 
CodecLock: true
DtmfMode: 
Expires: 3600
FromUser: 
Tel: true
TranscodeDtmf: true
AssociatedAddresses: inb.oun.d.ip 
InterOffice: false
DialPlan: 
UseEpid: false
CidUpdate: 
Ignore18xSDP: false
UserHdr: 
Diversion: 
Colines: 
DialogPermission: 

 

I would be willing to make snomone a temp account if they want to work with Vitelity. I have been trying Sotel lately and everything has been running great. some of the trunk options are wrong on the wiki though. I will post the changes I made later in a post on that.

[Pablo]

I have it working pretty good, dialing out is sometimes quick and sometimes a 10 second wait. Here is my IP registration setup:

 

Trunk 17

Name: Vitelity

Type: proxy

...

[/code]

 

I would be willing to make snomone a temp account if they want to work with Vitelity. I have been trying Sotel lately and everything has been running great. some of the trunk options are wrong on the wiki though. I will post the changes I made later in a post on that.

 

Steve,

When you say that here's your "IP registration" set-up; what do you mean by that, exactly? There're two ways to connect a trunk to Vitelity: (i) SIP Registration or (ii) IP authentication. If you're willing to tinker a little bit, you may be able to get rid of that 10-second delay by employing the workaround I described in a different forum topic (see post #12). If you follow my example, you'll want to make sure that you change the "type" variable on each trunk from "proxy" to "registration." In addition, you'll need to log into your customer portal at Vitelity and create a login ID & password for a "Sub Account" under the DIDs tab.

[Steve B]

Steve,

When you say that here's your "IP registration" set-up; what do you mean by that, exactly? There're two ways to connect a trunk to Vitelity: (i) SIP Registration or (ii) IP authentication. If you're willing to tinker a little bit, you may be able to get rid of that 10-second delay by employing the workaround I described in a different forum topic (see post #12). If you follow my example, you'll want to make sure that you change the "type" variable on each trunk from "proxy" to "registration." In addition, you'll need to log into your customer portal at Vitelity and create a login ID & password for a "Sub Account" under the DIDs tab.

 

Some providers have said IP registration which is just an IP authentication that I have set up as a proxy server. Are you monitoring your SIP registrations with Vitelity to see when they are going up and down. I will try the in and and out and see if the registration is more reliable than before. I would get a lot of 408 errors when I was running a SIP registration. Thank you, I will report back a bit later and tell you how it is working.

[Steve B]

Some providers have said IP registration which is just an IP authentication that I have set up as a proxy server. Are you monitoring your SIP registrations with Vitelity to see when they are going up and down. I will try the in and and out and see if the registration is more reliable than before. I would get a lot of 408 errors when I was running a SIP registration. Thank you, I will report back a bit later and tell you how it is working.

My connection to Vitelity went 408 unreachable 64 times between 12:30 yesterday and 8:00 AM this morning. The rest of my trunks stayed up without a problem. Is there a reason snomONE takes 60 seconds to re-register instead of an immediate re-register on 408, 401 then every 10 seconds until it comes back up. A minute can be an eternity on some systems. At least let us be able to make the decision how we want it to re-register.

[Vodia PBX]

My connection to Vitelity went 408 unreachable 64 times between 12:30 yesterday and 8:00 AM this morning. The rest of my trunks stayed up without a problem. Is there a reason snomONE takes 60 seconds to re-register instead of an immediate re-register on 408, 401 then every 10 seconds until it comes back up. A minute can be an eternity on some systems. At least let us be able to make the decision how we want it to re-register.

 

The PBX re-registers depending on what it is being told by the registrar. However you can override that (did you already?) with the "Keepalive Time". Then you can be 100 % sure this is not a problem with a too short registration interval.

[Steve B]

The PBX re-registers depending on what it is being told by the registrar. However you can override that (did you already?) with the "Keepalive Time". Then you can be 100 % sure this is not a problem with a too short registration interval.

I understand that part, I am talking about when the trunk loses registrations, such as a 408 error (I shouldn't have used the 401 error above in my description). It would be nice for the trunk to have an option of immediately re-registering and having a setting to be able to say how often to try and re-register after that. If we have to wait 60 seconds to re-register, this can/has lead to support calls. I have another system that allows us to set this under the SIP settings.

[Vodia PBX]

Well when registration fails, the system has already re-sent the REGISTER messages many times (500 ms, 1 s, 2 s, 4 s, 8 s, 8 s, 8 s). Giving it a "break" for 60 seconds does not sound unreasonable to me. You also have to keep in mind that too many registrations may be DoS for the registrar. The key question here is why the registration fails so often. If other trunks stay up all the time that is a hint that the internet connectivity is stable (which is usually the problem); the only think that I can think of is that the registrar expects the registration on a different IP address for fail-over or load balancing purposes, which causes problems. Also you have to keep in mind that the DNS server might also play a critical role in this game. In order to rule that out I would out an IP address in the outbound proxy to see if that could be the issue.

[Steve B]

Well when registration fails, the system has already re-sent the REGISTER messages many times (500 ms, 1 s, 2 s, 4 s, 8 s, 8 s, 8 s). Giving it a "break" for 60 seconds does not sound unreasonable to me. You also have to keep in mind that too many registrations may be DoS for the registrar. The key question here is why the registration fails so often. If other trunks stay up all the time that is a hint that the internet connectivity is stable (which is usually the problem); the only think that I can think of is that the registrar expects the registration on a different IP address for fail-over or load balancing purposes, which causes problems. Also you have to keep in mind that the DNS server might also play a critical role in this game. In order to rule that out I would out an IP address in the outbound proxy to see if that could be the issue.

 

I finally got to it, here is the log file, the funny thing is is that the PBX gets a 200 OK back from Vitelity then says the trunk is 408:

 

May  3 16:41:51 BestPBX Trunk 22: Preparing for re-registration 
May  3 16:41:51 BestPBX Trunk Vitelity Outbound: Sending registration to 64.2.x.x 
May  3 16:41:51 BestPBX Resolve 2738182: udp 64.2.x.x 5060 
May  3 16:41:51 BestPBX SIP Tx udp:64.2.x.x:5060: REGISTER sip: SIP/2.0#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-d9f3be5373cd55817229d26d4ec47834;rport#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88015 REGISTER#015#012Max-Forwards: 70#015#012Contact: <sip:**myusername**@24.119.x.x:5060;transport=udp;line=b6d767d2>;+sip.instance="<urn:uuid:f282f982-9f3c-4c3e-91f6-bb4682171d9b>"#015#012User-Agent: snomONE/4.5.0.1090 Epsilon Geminids#015#012Supported: outbound#015#012Expires: 3600#015#012Content-Length: 0#015#012#015
May  3 16:41:51 BestPBX SIP Rx udp:64.2.x.x:5060: SIP/2.0 100 Trying#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-d9f3be5373cd55817229d26d4ec47834;received=24.119.x.x;rport=5060#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88015 REGISTER#015#012User-Agent: packetrino#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO#015#012Supported: replaces#015#012Content-Length: 0#015#012#015
May  3 16:41:51 BestPBX Message repetition, packet dropped 
May  3 16:41:51 BestPBX SIP Rx udp:64.2.x.x:5060: SIP/2.0 401 Unauthorized#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-d9f3be5373cd55817229d26d4ec47834;received=24.119.x.x;rport=5060#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>;tag=as04681bd6#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88015 REGISTER#015#012User-Agent: packetrino#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO#015#012Supported: replaces#015#012WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="29c9acdc"#015#012Content-Length: 0#015#012#015
May  3 16:41:51 BestPBX Answer challenge with username **myusername** 
May  3 16:41:51 BestPBX Resolve 2738183: udp 64.2.x.x 5060 udp:1 
May  3 16:41:51 BestPBX SIP Tx udp:64.2.x.x:5060: REGISTER sip: SIP/2.0#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-15acf27157a93b1e9491d99cd18899c1;rport#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88016 REGISTER#015#012Max-Forwards: 70#015#012Contact: <sip:**myusername**@24.119.x.x:5060;transport=udp;line=b6d767d2>;+sip.instance="<urn:uuid:f282f982-9f3c-4c3e-91f6-bb4682171d9b>"#015#012User-Agent: snomONE/4.5.0.1090 Epsilon Geminids#015#012Supported: outbound#015#012Authorization: Digest realm="asterisk",nonce="29c9acdc",response="67a94278dd46790b5a437d1c89c79b8a",username="**myusername**",uri="sip:",algorithm=MD5#015#012Expires: 3600#015#012Content-Length: 0#015#012#015
May  3 16:41:51 BestPBX Message repetition, packet dropped 
May  3 16:41:52 BestPBX SIP Rx udp:64.2.x.x:5060: SIP/2.0 100 Trying#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-15acf27157a93b1e9491d99cd18899c1;received=24.119.x.x;rport=5060#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88016 REGISTER#015#012User-Agent: packetrino#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO#015#012Supported: replaces#015#012Content-Length: 0#015#012#015
May  3 16:41:52 BestPBX Message repetition, packet dropped 
May  3 16:41:52 BestPBX SIP Rx udp:64.2.x.x:5060: SIP/2.0 200 OK#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-15acf27157a93b1e9491d99cd18899c1;received=24.119.x.x;rport=5060#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>;tag=as04681bd6#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88016 REGISTER#015#012User-Agent: packetrino#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO#015#012Supported: replaces#015#012Expires: 60#015#012Contact: <sip:**myusername**@24.119.x.x:5060;transport=udp;line=b6d767d2>;expires=60#015#012Date: Fri, 03 May 2013 23:02:39 GMT#015#012Content-Length: 0#015#012#015
May  3 16:41:52 BestPBX Trunk 22: setup callback to send re-registration after 30 seconds 
May  3 16:41:53 BestPBX Clearing outbound proxy for trunk 22 (Vitelity Outbound) 
May  3 16:41:53 BestPBX Registration on trunk 22 (Vitelity Outbound) failed with code 408. Retry in 60 seconds 
May  3 16:41:53 BestPBX Trunk status Vitelity Outbound (22) changed to "408 Request Timeout" (Registration failed, retry after 60 seconds) 
May  3 16:41:53 BestPBX DNS: Request mail.**maildomain**.com from server 24.166.x.x 
May  3 16:41:53 BestPBX DNS: Add CNAME mail.**maildomain**.com **maildomain**.com (ttl=14400) 
May  3 16:41:53 BestPBX DNS: erasing AAAA mail.**maildomain**.com, id 9855 retry count 0, 
May  3 16:41:53 BestPBX DNS: Request **maildomain**.com from server 24.166.x.x 
May  3 16:41:54 BestPBX DNS: Add AAAA **maildomain**.com  (ttl=60) 
May  3 16:41:54 BestPBX DNS: erasing AAAA **maildomain**.com, id 9856 retry count 0, 
May  3 16:41:54 BestPBX DNS: Request **maildomain**.com from server 24.166.x.x 
May  3 16:41:54 BestPBX DNS: Add A **maildomain**.com 69.89.x.x (ttl=14400) 
May  3 16:41:54 BestPBX DNS: erasing A **maildomain**.com, id 9857 retry count 0, 
------
May  3 16:42:53 BestPBX Trunk 22: Preparing for re-registration 
May  3 16:42:53 BestPBX Trunk 22: sending discover message for  
May  3 16:42:53 BestPBX Resolve 2738188: discover 64.2.x.x 
May  3 16:42:53 BestPBX Trunk 22: Received reply for discover method 
May  3 16:42:53 BestPBX Trunk 22 (Vitelity Outbound) is associated with the following addresses: 64.2.x.x 
May  3 16:42:53 BestPBX Trunk Vitelity Outbound: Sending registration to 64.2.x.x 
May  3 16:42:53 BestPBX Resolve 2738189: url sip:64.2.x.x 
May  3 16:42:53 BestPBX Resolve 2738189: udp 64.2.x.x 5060 
May  3 16:42:53 BestPBX SIP Tx udp:64.2.x.x:5060: REGISTER sip: SIP/2.0#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-08db4856e9b1ff185c6580d17c56c9f8;rport#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88017 REGISTER#015#012Max-Forwards: 70#015#012Contact: <sip:**myusername**@24.119.x.x:5060;transport=udp;line=b6d767d2>;+sip.instance="<urn:uuid:f282f982-9f3c-4c3e-91f6-bb4682171d9b>"#015#012User-Agent: snomONE/4.5.0.1090 Epsilon Geminids#015#012Supported: outbound#015#012Expires: 3600#015#012Content-Length: 0#015#012#015
May  3 16:42:53 BestPBX SIP Rx udp:64.2.x.x:5060: SIP/2.0 100 Trying#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-08db4856e9b1ff185c6580d17c56c9f8;received=24.119.x.x;rport=5060#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88017 REGISTER#015#012User-Agent: packetrino#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO#015#012Supported: replaces#015#012Content-Length: 0#015#012#015
May  3 16:42:53 BestPBX Message repetition, packet dropped 
May  3 16:42:53 BestPBX SIP Rx udp:64.2.x.x:5060: SIP/2.0 401 Unauthorized#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-08db4856e9b1ff185c6580d17c56c9f8;received=24.119.x.x;rport=5060#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>;tag=as0fcb37c9#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88017 REGISTER#015#012User-Agent: packetrino#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO#015#012Supported: replaces#015#012WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="291177d1"#015#012Content-Length: 0#015#012#015
May  3 16:42:53 BestPBX Answer challenge with username **myusername** 
May  3 16:42:53 BestPBX Resolve 2738190: udp 64.2.x.x 5060 udp:1 
May  3 16:42:53 BestPBX SIP Tx udp:64.2.x.x:5060: REGISTER sip: SIP/2.0#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-e6721577bd050373f62092372d8b8669;rport#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88018 REGISTER#015#012Max-Forwards: 70#015#012Contact: <sip:**myusername**@24.119.x.x:5060;transport=udp;line=b6d767d2>;+sip.instance="<urn:uuid:f282f982-9f3c-4c3e-91f6-bb4682171d9b>"#015#012User-Agent: snomONE/4.5.0.1090 Epsilon Geminids#015#012Supported: outbound#015#012Authorization: Digest realm="asterisk",nonce="291177d1",response="b3933bbcffb57db488bf9fa64d764143",username="**myusername**",uri="sip:",algorithm=MD5#015#012Expires: 3600#015#012Content-Length: 0#015#012#015
May  3 16:42:53 BestPBX Message repetition, packet dropped 
May  3 16:42:53 BestPBX SIP Rx udp:64.2.x.x:5060: SIP/2.0 100 Trying#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-e6721577bd050373f62092372d8b8669;received=24.119.x.x;rport=5060#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88018 REGISTER#015#012User-Agent: packetrino#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO#015#012Supported: replaces#015#012Content-Length: 0#015#012#015
May  3 16:42:53 BestPBX Message repetition, packet dropped 
May  3 16:42:53 BestPBX SIP Rx udp:64.2.x.x:5060: SIP/2.0 200 OK#015#012Via: SIP/2.0/UDP 24.119.x.x:5060;branch=z9hG4bK-e6721577bd050373f62092372d8b8669;received=24.119.x.x;rport=5060#015#012From: "Vitelity Outbound" <sip:**myusername**@>;tag=1864809879#015#012To: "Vitelity Outbound" <sip:**myusername**@>;tag=as0fcb37c9#015#012Call-ID: eixyvo4y@pbx#015#012CSeq: 88018 REGISTER#015#012User-Agent: packetrino#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO#015#012Supported: replaces#015#012Expires: 60#015#012Contact: <sip:**myusername**@24.119.x.x:5060;transport=udp;line=b6d767d2>;expires=60#015#012Date: Fri, 03 May 2013 23:03:41 GMT#015#012Content-Length: 0#015#012#015
May  3 16:42:53 BestPBX Trunk status Vitelity Outbound (22) changed to "200 OK" (Refresh interval 30 seconds) 
May  3 16:42:53 BestPBX Trunk 22: setup callback to send re-registration after 30 seconds 

 

I have the PCAP also, just have to go get it off the server.

[Vodia PBX]

It is indeed strange. Could this be because the previous REGISTER ended up in a timeout after the PBX has already sent out a new registration? We'll put something into the code that will help find out if that is the case. But if this should be the case, then the PBX would override the previously received 30 seconds timeout and re-try after 60 seconds, leaving a few seconds gap where the trunk would really not be registered. It would be "missing a beat". Anyway, thanks for the good trace. Hopefully the next version will be even more robust in that area.