From SME server Forum, re Pi and IAX registration.

[drifting]

Seems it does not like the registration?
Confirmed the client was ok, connected to my old Sail system. Tried also recreating the account, even simplified the passwords. Same thing.

1072.925956    10.0.0.43 -> 10.0.0.9     IAX2 135 IAX, source call# 10, timestamp 1ms REGREQ
1072.927933     10.0.0.9 -> 10.0.0.43    IAX2 75 IAX, source call# 3482, timestamp 1ms REGAUTH
1072.929765    10.0.0.43 -> 10.0.0.9     IAX2 116 IAX, source call# 10, timestamp 5ms REGREQ
1072.930775     10.0.0.9 -> 10.0.0.43    IAX2 54 IAX, source call# 3482, timestamp 5ms ACK
1072.931837     10.0.0.9 -> 10.0.0.43    IAX2 79 IAX, source call# 3482, timestamp 5ms REGREJ

[drifting]

Interestingly I have the same problem with my SARK200 unit? Really odd, client has a connection perfectly ok to an elderly SME8 and Sail 3.* with IAX.

Most odd.

Paul.

[sarkdevs]

IAX is fine on ALL debian releases of SARK; there are no known issues and we have many Debian boxes happily running IAX2 trunks.   The only issue is that if your SARK box doesn't have a timing source then you can't run trunk=yes; nothing to do with SARK, this is an Asterisk requirement.   If your registration is failing then you've specified something incorrectly, either in the registration string or in the firewall(s) which protect the boxes.   

[drifting]

Hi Long delay on my part.

It was not the trunks that were an issue, it was the IAX clients. Never did get them to work, but was not a major hardship to use SIP instead.

P