Jump to content

Teliax Issues


Worm78
 Share

Recommended Posts

Anyone else seeing trunk issues using Teliax?

 

They have had some ups and downs for the last month. I move to another Trunk and everything is fine. That list of OK trunks started to dwindle. They explained they were just doing some updates. Today they told me they did the final upgrade on the last lax.teliax.net trunk I was using. Since then I cannot connect. They have said several Asterisks users who had to make some configuration changes.

I currently get a 481 Call Does Not Exist (Registration failed, retry after 60 seconds). I have the information correct. The selected server is correct on the dashboard provided by Teliax.

 

Anyone else figured out what to change? They can give me nothing more then invalid user ID.

 

Any ideas?

 

note the call id: field. Teliax thinks this is the issue.

 

Below is the log

Logfile

Clear or Reload the log.

 

[2] 20081119145322: Web interface triggered reregistration of trunk 9

[8] 20081119145322: route_pending_packet -1097: entry=url sip:lax.teliax.net

[8] 20081119145322: route_pending_packet -1097: entry=naptr lax.teliax.net

[8] 20081119145322: route_pending_packet -1097: entry=srv tls _sips._tcp.lax.teliax.net

[8] 20081119145322: DNS cache_lookup: dns_srv _sips._tcp.lax.teliax.net ->

[8] 20081119145322: route_pending_packet -1097: entry=srv tcp _sip._tcp.lax.teliax.net

[8] 20081119145322: DNS cache_lookup: dns_srv _sip._tcp.lax.teliax.net ->

[8] 20081119145322: route_pending_packet -1097: entry=srv udp _sip._udp.lax.teliax.net

[8] 20081119145322: DNS cache_lookup: dns_srv _sip._udp.lax.teliax.net ->

[8] 20081119145322: route_pending_packet -1097: entry=a udp lax.teliax.net 5060

[8] 20081119145322: DNS cache_lookup: dns_a lax.teliax.net -> 74.201.8.23

[8] 20081119145322: route_pending_packet -1097: entry=udp 74.201.8.23 5060

[8] 20081119145322: Trunk 9 (Teliax 1) has outbound proxy udp:74.201.8.23:5060

[8] 20081119145322: route_pending_packet -1098: entry=udp 74.201.8.23 5060

[8] 20081119145322: Send Packet REGISTER

[9] 20081119145322: SIP Tx udp:74.201.8.23:5060:

REGISTER sip:lax.teliax.net SIP/2.0

Via: SIP/2.0/UDP 75.149.200.210:5060;branch=z9hG4bK-1a001a5300f78f19b8522ea17d553fa4;rport

From: "brichter" <sip:brichter@lax.teliax.net>;tag=26524

To: "brichter" <sip:brichter@lax.teliax.net>

Call-ID: ttagjj3g@pbx

CSeq: 124 REGISTER

Max-Forwards: 70

Contact: <sip:brichter@75.149.200.210:5060;transport=udp;line=45c48cce>;reg-id=1;+sip.instance="<urn:uuid:159f4fe2-2ba5-48e2-af0c-549b66b46747>"

User-Agent: pbxnsip-PBX/1.5.2.10a

Expires: 3600

Content-Length: 0

 

[9] 20081119145322: SIP Rx udp:74.201.8.23:5060:

SIP/2.0 401 Unauthorized

Via: SIP/2.0/UDP 75.149.200.210:5060;branch=z9hG4bK-1a001a5300f78f19b8522ea17d553fa4;rport=5060

From: "brichter" <sip:brichter@lax.teliax.net>;tag=26524

To: "brichter" <sip:brichter@lax.teliax.net>;tag=vyegX37aDjQHc

Call-ID: ttagjj3g@pbx

CSeq: 124 REGISTER

User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-10454M

Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO, PUBLISH

Supported: timer, precondition, path, replaces

WWW-Authenticate: Digest realm="lax.teliax.net", nonce="2e0a5f73-73b6-dd11-8406-00114336c25a", algorithm=MD5, qop="auth"

Content-Length: 0

 

[8] 20081119145322: route_pending_packet -1099: entry=udp 74.201.8.23 5060

[8] 20081119145322: Send Packet REGISTER

[9] 20081119145322: SIP Tx udp:74.201.8.23:5060:

REGISTER sip:lax.teliax.net SIP/2.0

Via: SIP/2.0/UDP 75.149.200.210:5060;branch=z9hG4bK-b18664ba5bb745a6d3828102d36620bb;rport

From: "brichter" <sip:brichter@lax.teliax.net>;tag=26524

To: "brichter" <sip:brichter@lax.teliax.net>;tag=vyegX37aDjQHc

Call-ID: ttagjj3g@pbx

CSeq: 125 REGISTER

Max-Forwards: 70

Contact: <sip:brichter@75.149.200.210:5060;transport=udp;line=45c48cce>;reg-id=1;+sip.instance="<urn:uuid:159f4fe2-2ba5-48e2-af0c-549b66b46747>"

User-Agent: pbxnsip-PBX/1.5.2.10a

Authorization: Digest realm="lax.teliax.net",nonce="2e0a5f73-73b6-dd11-8406-00114336c25a",response="601290b0c34cfa273a4ca9dfdf94ce45",username="brichter",uri="sip:lax.teliax.net",qop=auth,nc=00000001,cnonce="edb10a67",stale=true,algorithm=MD5

Expires: 3600

Content-Length: 0

 

[9] 20081119145322: SIP Rx udp:74.201.8.23:5060:

SIP/2.0 481 Call Does Not Exist

Via: SIP/2.0/UDP 75.149.200.210:5060;branch=z9hG4bK-b18664ba5bb745a6d3828102d36620bb;rport=5060

From: "brichter" <sip:brichter@lax.teliax.net>;tag=26524

To: "brichter" <sip:brichter@lax.teliax.net>;tag=vyegX37aDjQHc

Call-ID: ttagjj3g@pbx

CSeq: 125 REGISTER

User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-10454M

Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO, PUBLISH

Supported: timer, precondition, path, replaces

Content-Length: 0

 

[5] 20081119145322: Registration on trunk 9 (Teliax 1) failed. Retry in 60 secon

Link to comment
Share on other sites

Anyone else seeing trunk issues using Teliax?

 

They have had some ups and downs for the last month. I move to another Trunk and everything is fine. That list of OK trunks started to dwindle. They explained they were just doing some updates. Today they told me they did the final upgrade on the last lax.teliax.net trunk I was using. Since then I cannot connect. They have said several Asterisks users who had to make some configuration changes.

I currently get a 481 Call Does Not Exist (Registration failed, retry after 60 seconds). I have the information correct. The selected server is correct on the dashboard provided by Teliax.

 

Anyone else figured out what to change? They can give me nothing more then invalid user ID.

 

Any ideas?

 

[...]

 

[9] 20081119145322: SIP Rx udp:74.201.8.23:5060:

SIP/2.0 481 Call Does Not Exist

Via: SIP/2.0/UDP 75.149.200.210:5060;branch=z9hG4bK-b18664ba5bb745a6d3828102d36620bb;rport=5060

From: "brichter" <sip:brichter@lax.teliax.net>;tag=26524

To: "brichter" <sip:brichter@lax.teliax.net>;tag=vyegX37aDjQHc

Call-ID: ttagjj3g@pbx

CSeq: 125 REGISTER

User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-10454M

Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO, PUBLISH

Supported: timer, precondition, path, replaces

Content-Length: 0

 

[5] 20081119145322: Registration on trunk 9 (Teliax 1) failed. Retry in 60 secon

 

Hmm, not sure why FreeSWITCH replies with with a "call" when trying to register. But that looks like a bug to me. Or maybe it is something trivial like that user really does not exist.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...