SIP/2.0 408 Request timeout on Registration on a fresh installation
748 views
Skip to first unread message
Kinshuk Bairagi
Jan 11, 2018, 9:18:11 AM1/11/18
to sipxcom-users
Hi
What am I doing wrong here?
I am trying to setup sipxcom, and have setup on a single server as per the getting started guide and created the users. But now when I try to register the sip phone I keep getting `SIP/2.0 408 Request timeout.` and the registration fails. Any pointers would be helpful.
Here is the ngrep output
T 172.X.X.36:61969 -> 10.X.X.59:5060 [AP]REGISTER sip:sip.domain.net;transport=TCP SIP/2.0.Via: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---b1af141e0e398c00;rport.Max-Forwards: 70.Contact: <sip:2...@172.X.X.36:35278;rinstance=e8853b5243611a47;transport=tcp>.To: <sip:2...@sip.domain.net;transport=TCP>.From: <sip:2...@sip.domain.net;transport=TCP>;tag=0538a964.Call-ID: Si3w3IuqsLnkMxRJuJ07_w...CSeq: 61 REGISTER.Expires: 600.Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE.User-Agent: Z 5.2.7 rv2.8.67-mod.Allow-Events: presence, kpml, talk.Content-Length: 0..
T 10.X.X.59:5060 -> 172.X.X.36:61969 [AP]SIP/2.0 408 Request timeout.From: <sip:2...@sip.domain.net;transport=TCP>;tag=0538a964.To: <sip:2...@sip.domain.net;transport=TCP>;tag=4S804O.Call-Id: Si3w3IuqsLnkMxRJuJ07_w...Cseq: 61 REGISTER.Via: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---b1af141e0e398c00;rport=61969.Server: sipXecs/17.04 sipXecs/sipXproxy (Linux).Content-Length: 0..
Mircea Mihai Costache
Jan 11, 2018, 9:24:15 AM1/11/18
to Kinshuk Bairagi, sipxcom-users
Probably your user is not replicated in mongodb. Increase Registrar log level and try to see in registrar logs whtas going on
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/4715433f-33f4-49b3-a086-02ab80738ec1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Kinshuk Bairagi
Jan 11, 2018, 9:30:55 AM1/11/18
to sipxcom-users
I verified it is in mongo ( I have a single node system now )
Any idea what is going on? I am using Zopier5/X-Lite as client and it works with all other servers.
Here is what I see in registration logs
"2018-01-11T14:11:35.785055Z":86:SIP:INFO:sipxcom-alpha.localdomain:SipTcpServerBrokerListener-5:7f9d469da700:sipxregistry:"SipClient[SipClientTcp-32]::_ created TCP unshared socket 10: host '' '172.X.X.36' port 62867, local IP '10.X.X.59' port -1""2018-01-11T14:11:37.756634Z":87:INCOMING:INFO:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"Read SIP message:\n----Local Host:10.X.X.59---- Port: 5060----\n----Remote Host:172.X.X.36---- Port: 62867----\nREGISTER sip:sip.domain.net;transport=TCP SIP/2.0.\r\nVia: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---d6ec47bc0faa2d2f;rport.\r\nMax-Forwards: 70.\r\nContact: <sip:2...@172.X.X.36:35278;rinstance=e8853b5243611a47;transport=tcp>.\r\nTo: <sip:2...@sip.domain.net;transport=TCP>.\r\nFrom: <sip:2...@sip.domain.net;transport=TCP>;tag=0538a964.\r\nCall-ID: Si3w3IuqsLnkMxRJuJ07_w...\r\nCSeq: 1 REGISTER.\r\nExpires: 600.\r\nAllow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE.\r\nUser-Agent: Z 5.2.7 rv2.8.67-mod.\r\nAllow-Events: presence, kpml, talk.\r\nContent-Length: 0.\r\n.\r\n\r\n====================END====================\n""2018-01-11T14:11:37.757036Z":88:SIP:ERR:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"Url::parseString error - expected end of url or field parameter ';name=' at offset 40 in '<sip:2...@sip.domain.net;transport=TCP>.'""2018-01-11T14:11:37.757215Z":89:SIP:ERR:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"Url::parseString error - expected end of url or field parameter ';name=' at offset 40 in '<sip:2...@sip.domain.net;transport=TCP>.'""2018-01-11T14:11:37.757542Z":90:SIP:INFO:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"SipProtocolServerBase::findExistingClientForDestination found good flow SipClientTcp-32 for target 172.X.X.36:35278""2018-01-11T14:11:37.757723Z":91:OUTGOING:INFO:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"SipUserAgent::sendTcp TCP SIP User Agent sent message:\n----Local Host:10.X.X.59---- Port: -1----\n----Remote Host:172.X.X.36---- Port: 35278----\nSIP/2.0 505 Version Not Supported\r\nFrom: <sip:2...@sip.domain.net;transport=TCP>;tag=0538a964.\r\nTo: <sip:2...@sip.domain.net;transport=TCP>.;tag=IRi`_S\r\nCall-Id: Si3w3IuqsLnkMxRJuJ07_w...\r\nCseq: 1 REGISTER.\r\nVia: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---d6ec47bc0faa2d2f;rport.\r\nWarning: 399 10.X.X.59 \"Expected SIP/2.0\"\r\nContent-Type: message/sipfrag\r\nUser-Agent: sipXecs/17.04 sipXecs/registry (Linux)\r\nContent-Length: 640\r\n\r\nREGISTER sip:sip.domain.net;transport=TCP SIP/2.0.\r\nVia: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---d6ec47bc0faa2d2f;rport.\r\nMax-Forwards: 70.\r\nContact: <sip:2...@172.X.X.36:35278;rinstance=e8853b5243611a47;transport=tcp>.\r\nTo: <sip:2...@sip.domain.net;transport=TCP>.\r\nFrom: <sip:2...@sip.domain.net;transport=TCP>;tag=0538a964.\r\nCall-Id: Si3w3IuqsLnkMxRJuJ07_w...\r\nCseq: 1 REGISTER.\r\nExpires: 600.\r\nAllow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE.\r\nUser-Agent: Z 5.2.7 rv2.8.67-mod.\r\nAllow-Events: presence, kpml, talk.\r\nContent-Length: 0.\r\n.: \r\nDate: Thu, 11 Jan 2018 14:11:37 GMT\r\n\r\n--------------------END--------------------\n""2018-01-11T14:11:48.844913Z":92:KERNEL:INFO:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"OsConnectionSocket::read[4] error or EOF on fd 10, errno = 0 Success""2018-01-11T14:11:49.192578Z":93:KERNEL:INFO:sipxcom-alpha.localdomain::7f9d450d3700:sipxregistry:"OsConnectionSocket::~""2018-01-11T14:11:54.193673Z":94:SIP:NOTICE:sipxcom-alpha.localdomain::7f9d450d3700:sipxregistry:"SipTransactionList::removeOldTransactions deleting 1 of 1 transactions (0 busy)"Any idea what is going on? I am using Zopier5/X-Lite as client and it works with all other servers.
On Thursday, January 11, 2018 at 7:54:15 PM UTC+5:30, Mircea Mihai Costache wrote:
Probably your user is not replicated in mongodb. Increase Registrar log level and try to see in registrar logs whtas going on
On 11 Jan 2018 4:18 pm, "Kinshuk Bairagi" <kinsh...@gmail.com> wrote:
HiI am trying to setup sipxcom, and have setup on a single server as per the getting started guide and created the users. But now when I try to register the sip phone I keep getting `SIP/2.0 408 Request timeout.` and the registration fails. Any pointers would be helpful.Here is the ngrep output
What am I doing wrong here?
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
Mircea Mihai Costache
Jan 11, 2018, 9:32:57 AM1/11/18
to Kinshuk Bairagi, sipxcom-users
Cant see it very well on my cell but smels like a bug, or at least one char from you extension is messing with sip stack
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/b5cd14b7-99d5-4159-8731-c86bbba0e7da%40googlegroups.com.
Mircea Mihai Costache
Jan 11, 2018, 9:48:37 AM1/11/18
to Kinshuk Bairagi, sipxcom-users
I think the ending . is wrong here, see that every header ends with a .
----Remote Host:172.X.X.36---- Port: 62867----
REGISTER sip:sip.domain.net;transport=TCP SIP/2.0.
Via: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---d6ec47bc0faa2d2f;rport.
Max-Forwards: 70.
Contact: <sip:2...@172.X.X.36:35278;rinstance=e8853b5243611a47;transport=tcp>.
To: <sip:2...@sip.domain.net;transport=TCP>.
From: <sip:2...@sip.domain.net;transport=TCP>;tag=0538a964.
Call-ID: Si3w3IuqsLnkMxRJuJ07_w...
CSeq: 1 REGISTER.
Expires: 600.
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE.
User-Agent: Z 5.2.7 rv2.8.67-mod.
Allow-Events: presence, kpml, talk.
Content-Length: 0.
If Joegen is still arrounf he can enlighten us :)
Or else you could use a different UA that dont break things
Kinshuk Bairagi
Jan 11, 2018, 10:49:54 AM1/11/18
to Mircea Mihai Costache, sipxcom-users
Okay, there are some errors with dns too reported, I am trying to get that fixed first and then will try again.
This particular issue could have been due to a manual registration attempt directly to port 5070, which I attempted since I don't find any other client attempts in this log. All others have ended in dns error in sipxproxy log.
Thanks for your help, let me try to get dns error resolved and retry again.
On 11 Jan 2018 8:18 pm, "Mircea Mihai Costache" <costache.m...@gmail.com> wrote:
I think the ending . is wrong here, see that every header ends with a .----Remote Host:172.X.X.36---- Port: 62867----REGISTER sip:sip.domain.net;transport=TCP SIP/2.0.Via: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---d6ec47bc0faa2d2f;rport.Max-Forwards: 70.Contact: <sip:2...@172.X.X.36:35278;rinstance=e8853b5243611a47;transport=tcp>.To: <sip:2...@sip.domain.net;transport=TCP>.From: <sip:2...@sip.domain.net;transport=TCP>;tag=0538a964.Call-ID: Si3w3IuqsLnkMxRJuJ07_w...CSeq: 1 REGISTER.Expires: 600.Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE.User-Agent: Z 5.2.7 rv2.8.67-mod.Allow-Events: presence, kpml, talk.Content-Length: 0.If Joegen is still arrounf he can enlighten us :)Or else you could use a different UA that dont break things
Michael Picher
Jan 11, 2018, 10:51:49 AM1/11/18
to Kinshuk Bairagi, Mircea Mihai Costache, sipxcom-users
Yea, DNS is kinda important ;-)
Michael Picher, VP of Product Management
eZuce, Inc.
300 Brickstone Square
Suite 104
Andover, MA. 01810
Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you.
On Thu, Jan 11, 2018 at 10:49 AM, Kinshuk Bairagi <kinsh...@gmail.com> wrote:
Okay, there are some errors with dns too reported, I am trying to get that fixed first and then will try again.This particular issue could have been due to a manual registration attempt directly to port 5070, which I attempted since I don't find any other client attempts in this log. All others have ended in dns error in sipxproxy log.Thanks for your help, let me try to get dns error resolved and retry again.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CACa8_yop5iNCTa_%2B%3D1Yh0kJU9%3DfXHdssu77a-oD_OQHDkJzHmQ%40mail.gmail.com.
George Niculae
Jan 11, 2018, 11:03:16 AM1/11/18
to Kinshuk Bairagi, Mircea Mihai Costache, sipxcom-users
Registrations should happen against port 5060 that is proxy
George
On Jan 11, 2018 5:49 PM, "Kinshuk Bairagi" <kinsh...@gmail.com> wrote:
Okay, there are some errors with dns too reported, I am trying to get that fixed first and then will try again.This particular issue could have been due to a manual registration attempt directly to port 5070, which I attempted since I don't find any other client attempts in this log. All others have ended in dns error in sipxproxy log.Thanks for your help, let me try to get dns error resolved and retry again.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CACa8_yop5iNCTa_%2B%3D1Yh0kJU9%3DfXHdssu77a-oD_OQHDkJzHmQ%40mail.gmail.com.
Joegen Baclor
Jan 12, 2018, 12:02:45 AM1/12/18
to George Niculae, Kinshuk Bairagi, Mircea Mihai Costache, sipxcom-users
Smells like a DNS issue to me indeed.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CALLzRjYEtd6je_YLW%3DsiVHaa7bAnFUqHHEFs6dFaGK75v8%2BVwQ%40mail.gmail.com.
Kinshuk Bairagi
Jan 13, 2018, 4:35:53 PM1/13/18
to sipxcom-users
Thanks a lot, it turned out to be dns issue, once the dns issue was resolved everything worked properly :)
I have some queries regarding CDRs and HA, I will start a separate thread for it.
On Friday, January 12, 2018 at 10:32:45 AM UTC+5:30, JBaclor wrote:
Smells like a DNS issue to me indeed.
On Fri, Jan 12, 2018 at 12:03 AM, George Niculae <george.n...@gmail.com> wrote:
Registrations should happen against port 5060 that is proxyGeorge
On Jan 11, 2018 5:49 PM, "Kinshuk Bairagi" <kinsh...@gmail.com> wrote:
Okay, there are some errors with dns too reported, I am trying to get that fixed first and then will try again.This particular issue could have been due to a manual registration attempt directly to port 5070, which I attempted since I don't find any other client attempts in this log. All others have ended in dns error in sipxproxy log.Thanks for your help, let me try to get dns error resolved and retry again.
On 11 Jan 2018 8:18 pm, "Mircea Mihai Costache" <costache.m...@gmail.com> wrote:
I think the ending . is wrong here, see that every header ends with a .
----Remote Host:172.X.X.36---- Port: 62867----REGISTER sip:sip.domain.net;transport=TCP SIP/2.0.Via: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---d6ec47bc0faa2d2f;rport.Max-Forwards: 70.Contact: <sip:2...@172.X.X.36:35278;rinstance=e8853b5243611a47;transport=tcp>.
To: <sip...@sip.domain.net;transport=TCP>.From: <sip...@sip.domain.net;transport=TCP>;tag=0538a964.Call-ID: Si3w3IuqsLnkMxRJuJ07_w...
CSeq: 1 REGISTER.Expires: 600.Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE.User-Agent: Z 5.2.7 rv2.8.67-mod.Allow-Events: presence, kpml, talk.Content-Length: 0.
If Joegen is still arrounf he can enlighten us :)Or else you could use a different UA that dont break things
2018-01-11 16:32 GMT+02:00 Mircea Mihai Costache <costache.m...@gmail.com>:
Cant see it very well on my cell but smels like a bug, or at least one char from you extension is messing with sip stack
On 11 Jan 2018 4:30 pm, "Kinshuk Bairagi" <kinsh...@gmail.com> wrote:
I verified it is in mongo ( I have a single node system now )Here is what I see in registration logs
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/b5cd14b7-99d5-4159-8731-c86bbba0e7da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CACa8_yop5iNCTa_%2B%3D1Yh0kJU9%3DfXHdssu77a-oD_OQHDkJzHmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
saunder...@gmail.com
Oct 21, 2018, 11:31:54 PM10/21/18
to sipxcom-users
Hello all,
My IPTables is the default config that SipXCom built, but it has the ACCEPT policy for 5060 on TCP and UDP.
I've gotta be missing something i'm sure is simple, but this is my first time attempting a SIP server, so any help would be greatly appreciated :)
It seems I'm having a bit of trouble starting from a fresh install.
I'm not even getting firewall entries for my 408's upon registration.
NMAP displays the following when discovering open ports:
PORT STATE SERVICE VERSION
21/tcp open ftp vsftpd 2.2.2
22/tcp open ssh OpenSSH 5.3 (protocol 2.0)
53/tcp open domain
80/tcp open http Apache httpd 2.2.15
443/tcp open ssl/http Apache httpd 2.2.15
5060/tcp open sip sipXecs/18.04 sipXecs/sipXproxy (Linux) (Status: 408 Request timeout)
5432/tcp open postgresql PostgreSQL DBMy IPTables is the default config that SipXCom built, but it has the ACCEPT policy for 5060 on TCP and UDP.
My DNS records are as follows (redacted my true domain)
$TTL 1800@ IN SOA ns1.sipxcom.domain.com. root.sipxcom.domain.com. ( 197604549 ; serial# 1800 ; refresh, seconds 1800 ; retry, seconds 1800 ; expire, seconds 1800 ) ; minimum TTL, secondssipxcom.domain.com. IN NS sipxcom.domain.com.;; RECORDS: naptrsipxcom.domain.com. IN NAPTR 2 0 "s" "SIP+D2U" "" _sip._udpsipxcom.domain.com. IN NAPTR 1 0 "s" "SIP+D2T" "" _sip._tcp;; RECORDS: rr_sip._tcp IN SRV 30 10 5060 sipxcom.domain.com._sip._udp IN SRV 30 10 5060 sipxcom.domain.com._sips._tcp IN SRV 30 10 5061 sipxcom.domain.com._sip._tls IN SRV 30 10 5061 sipxcom.domain.com._sip._tcp.mwi IN SRV 30 10 5110 sipxcom.domain.com._sip._tcp.mwi.sipxcom IN SRV 10 10 5110 sipxcom.domain.com._sip._tcp.vm IN SRV 30 10 15060 sipxcom.domain.com._sip._tcp.vm.sipxcom IN SRV 10 10 15060 sipxcom.domain.com._sip._tcp.cbb IN SRV 30 10 15060 sipxcom.domain.com._sip._tcp.cbb.sipxcom IN SRV 10 10 15060 sipxcom.domain.com._sip._tcp.rr IN SRV 30 10 5070 sipxcom.domain.com._sip._tcp.rr.sipxcom IN SRV 10 10 5070 sipxcom.domain.com.
;; RECORDS: Asipxcom.domain.com. IN A 192.168.1.135
I've gotta be missing something i'm sure is simple, but this is my first time attempting a SIP server, so any help would be greatly appreciated :)
Todd Hodgen
Oct 22, 2018, 2:51:11 AM10/22/18
to saunder...@gmail.com, sipxcom-users
I would be more interested in seeing how you set it up – how did you install – from ISO? Server – is this on a dedicated server, cloud server, etc.
What did you use to install it – instructions from the WIKI?
So, rather than seeing your IP Tables, what is the nature of the issue you are having. What were you expecting and what happened. Can you get to the GUI?
Describe the installation – did it walk you through and then reboot and you can’t get to the GUI at all?
From the CLI, what do you see when you do a “service sipxecs status”
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/8f73b44f-535e-4670-9483-5dc0f2d35c6e%40googlegroups.com.
Michael Picher
Oct 22, 2018, 8:24:34 AM10/22/18
to sipxcom-users
And a better question... why are you hijacking an old thread?
Michael Picher
Oct 22, 2018, 7:18:30 PM10/22/18
to Joegen Baclor, George Niculae, Kinshuk Bairagi, Mircea Mihai Costache, sipxcom-users
It's never DNS! :-)
On Fri, Jan 12, 2018, 12:02 AM Joegen Baclor <joegen...@gmail.com> wrote:
Smells like a DNS issue to me indeed.
On Fri, Jan 12, 2018 at 12:03 AM, George Niculae <george.n...@gmail.com> wrote:
Registrations should happen against port 5060 that is proxyGeorge
On Jan 11, 2018 5:49 PM, "Kinshuk Bairagi" <kinsh...@gmail.com> wrote:
Okay, there are some errors with dns too reported, I am trying to get that fixed first and then will try again.This particular issue could have been due to a manual registration attempt directly to port 5070, which I attempted since I don't find any other client attempts in this log. All others have ended in dns error in sipxproxy log.Thanks for your help, let me try to get dns error resolved and retry again.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/b5cd14b7-99d5-4159-8731-c86bbba0e7da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CACa8_yop5iNCTa_%2B%3D1Yh0kJU9%3DfXHdssu77a-oD_OQHDkJzHmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CALLzRjYEtd6je_YLW%3DsiVHaa7bAnFUqHHEFs6dFaGK75v8%2BVwQ%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAA46EZw%3DzRWGD99RhF-OLwOa5eqJSTxH4eyW8Xwno0wk%2BKz%3D7A%40mail.gmail.com.
Todd Hodgen
Oct 22, 2018, 8:37:17 PM10/22/18
to Michael Picher, Joegen Baclor, George Niculae, Kinshuk Bairagi, Mircea Mihai Costache, sipxcom-users
Did you pull this out of the way way way back machine?
From: sipxco...@googlegroups.com [mailto:sipxco...@googlegroups.com]
On Behalf Of Michael Picher
Sent: Monday, October 22, 2018 4:18 PM
To: Joegen Baclor <joegen...@gmail.com>
Cc: George Niculae <george.n...@gmail.com>; Kinshuk Bairagi <kinsh...@gmail.com>; Mircea Mihai Costache <costache.m...@gmail.com>; sipxcom-users <sipxco...@googlegroups.com>
Subject: Re: [sipxcom-users] SIP/2.0 408 Request timeout on Registration on a fresh installation
It's never DNS! :-)
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CAAfvEN5dgP4zCyqLCd%3D4MdWv81mFd%3DSAOWF4T58mWiBVpq5Nhg%40mail.gmail.com.
Michael Picher
Oct 22, 2018, 8:57:21 PM10/22/18
to Todd Hodgen, Michael Picher, Joegen Baclor, George Niculae, Kinshuk Bairagi, Mircea Mihai Costache, sipxcom-users
Probably... I'm not that creative... But I'm very sarcastic.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/SN2PR07MB24931E1D83EC73CC031678A3FDF50%40SN2PR07MB2493.namprd07.prod.outlook.com.
saunder...@gmail.com
Oct 23, 2018, 11:08:59 PM10/23/18
to sipxcom-users
My apologies, I was coming off of a 70+ hour work week, and did not see the date when last posted. However, it was #1 on my Google search, despite how stale the thread was.
I've been having issues with sipxcom re-writing the DNS zones incorrectly, this making named fail. Specifically, adding two periods to the end of correct entries.
I've even terminated the sipxcom processes, edited the zones, chmod it to read only, and when the sipxcom processes come back online it re-writes it again.
As much as I would like to use sipxcom perform its own DNS, I might have to use an alternate.
Unless someone has some suggestions?
Any other issues I have I promise I will open a new thread :)
To: <sip...@sip.domain.net;transport=TCP>.
From: <sip...@sip.domain.net;transport=TCP>;tag=0538a964.
Call-ID: Si3w3IuqsLnkMxRJuJ07_w...
CSeq: 1 REGISTER.
Expires: 600.
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE.
User-Agent: Z 5.2.7 rv2.8.67-mod.
Allow-Events: presence, kpml, talk.
Content-Length: 0.
If Joegen is still arrounf he can enlighten us :)
Or else you could use a different UA that dont break things
2018-01-11 16:32 GMT+02:00 Mircea Mihai Costache <costache.m...@gmail.com>:
Cant see it very well on my cell but smels like a bug, or at least one char from you extension is messing with sip stack
On 11 Jan 2018 4:30 pm, "Kinshuk Bairagi" <kinsh...@gmail.com> wrote:
I verified it is in mongo ( I have a single node system now )
Here is what I see in registration logs
"2018-01-11T14:11:35.785055Z":86:SIP:INFO:sipxcom-alpha.localdomain:SipTcpServerBrokerListener-5:7f9d469da700:sipxregistry:"SipClient[SipClientTcp-32]::_ created TCP unshared socket 10: host '' '172.X.X.36' port 62867, local IP '10.X.X.59' port -1"
"2018-01-11T14:11:37.756634Z":87:INCOMING:INFO:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"Read SIP message:\n----Local Host:10.X.X.59---- Port: 5060----\n----Remote Host:172.X.X.36---- Port: 62867----\nREGISTER sip:sip.domain.net;transport=TCP SIP/2.0.\r\nVia: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---d6ec47bc0faa2d2f;rport.\r\nMax-Forwards: 70.\r\nContact: <sip:2...@172.X.X.36:35278;rinstance=e8853b5243611a47;transport=tcp>.\r\nTo: <sip...@sip.domain.net;transport=TCP>.\r\nFrom: <sip...@sip.domain.net;transport=TCP>;tag=0538a964.\r\nCall-ID: Si3w3IuqsLnkMxRJuJ07_w...\r\nCSeq: 1 REGISTER.\r\nExpires: 600.\r\nAllow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE.\r\nUser-Agent: Z 5.2.7 rv2.8.67-mod.\r\nAllow-Events: presence, kpml, talk.\r\nContent-Length: 0.\r\n.\r\n\r\n====================END====================\n"
"2018-01-11T14:11:37.757036Z":88:SIP:ERR:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"Url::parseString error - expected end of url or field parameter ';name=' at offset 40 in '<sip...@sip.domain.net;transport=TCP>.'"
"2018-01-11T14:11:37.757215Z":89:SIP:ERR:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"Url::parseString error - expected end of url or field parameter ';name=' at offset 40 in '<sip...@sip.domain.net;transport=TCP>.'"
"2018-01-11T14:11:37.757542Z":90:SIP:INFO:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"SipProtocolServerBase::findExistingClientForDestination found good flow SipClientTcp-32 for target 172.X.X.36:35278"
"2018-01-11T14:11:37.757723Z":91:OUTGOING:INFO:sipxcom-alpha.localdomain:SipClientTcp-32:7f9d3c098700:sipxregistry:"SipUserAgent::sendTcp TCP SIP User Agent sent message:\n----Local Host:10.X.X.59---- Port: -1----\n----Remote Host:172.X.X.36---- Port: 35278----\nSIP/2.0 505 Version Not Supported\r\nFrom: <sip...@sip.domain.net;transport=TCP>;tag=0538a964.\r\nTo: <sip...@sip.domain.net;transport=TCP>.;tag=IRi`_S\r\nCall-Id: Si3w3IuqsLnkMxRJuJ07_w...\r\nCseq: 1 REGISTER.\r\nVia: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---d6ec47bc0faa2d2f;rport.\r\nWarning: 399 10.X.X.59 \"Expected SIP/2.0\"\r\nContent-Type: message/sipfrag\r\nUser-Agent: sipXecs/17.04 sipXecs/registry (Linux)\r\nContent-Length: 640\r\n\r\nREGISTER sip:sip.domain.net;transport=TCP SIP/2.0.\r\nVia: SIP/2.0/TCP 172.X.X.36:35278;branch=z9hG4bK-524287-1---d6ec47bc0faa2d2f;rport.\r\nMax-Forwards: 70.\r\nContact: <sip:2...@172.X.X.36:35278;rinstance=e8853b5243611a47;transport=tcp>.\r\nTo: <sip...@sip.domain.net;transport=TCP>.\r\nFrom: <sip...@sip.domain.net;transport=TCP>;tag=0538a964.\r\nCall-Id: Si3w3IuqsLnkMxRJuJ07_w...\r\nCseq: 1 REGISTER.\r\nExpires: 600.\r\nAllow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE.\r\nUser-Agent: Z 5.2.7 rv2.8.67-mod.\r\nAllow-Events: presence, kpml, talk.\r\nContent-Length: 0.\r\n.: \r\nDate: Thu, 11 Jan 2018 14:11:37 GMT\r\n\r\n--------------------END--------------------\n"
George Niculae
Oct 23, 2018, 11:12:45 PM10/23/18
to saunder...@gmail.com, sipxcom-users
You can check Unmanaged options in DNS page so sipxcom won't alter files anymore
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/0a151c84-c610-47f8-b912-1319cbd28383%40googlegroups.com.
Michael Picher
Oct 24, 2018, 5:26:55 AM10/24/18
to George Niculae, saunder...@gmail.com, sipxco...@googlegroups.com
George is correct, however,sipXcom does not rewrite the dns config files incorrectly...
Maybe you entered the sip domain or server host name incorrectly when you installed.
Mike
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/CALLzRjbwrsW_pvQ19ocHp9-LWzb24LL2B1LaJtv-hA7xwJYCQQ%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages